Vulnerability Scan Result

Target:

https://phantom-sense-68c.notion.site/Top-Mistakes-New-Slot-Players-Make-1d58eecaa4e08004b794cec78329637a?pvs=4

Scanned target: https://phantom-sense-68c.notion.site/Top-Mistakes-New-Slot-Players-Make-1d58eecaa4e08004b794cec78329637a?pvs=4

Submitted: April 14, 2025 from SO

Public scan

Scan mode: Passive (non-intrusive)

Summary

medium

Info

Low

Medium

High

Critical

Screenshot

https://phantom-sense-68c.notion.site/Top-Mistakes-New-Slot-Players-Make-1d58eecaa4e08004b794cec78329637a?pvs=4

Title:	Your connected workspace for wiki, docs & projects \| Notion
Description:	A new tool that blends your everyday work apps into one. It's the all-in-one workspace for you and your team

IP Information

IP address	208.103.161.33
Country	US
AS number	-
Net name	-

IP address	208.103.161.32
Country	US
AS number	-
Net name	-

Open Ports

80/tcp	http	Cloudflare http proxy -
443/tcp	https	cloudflare -
8080/tcp	http	Cloudflare http proxy -
8443/tcp	http	cloudflare -

Web Technologies

Software / Version	Category
Amazon Web Services	PaaS
Amazon S3	CDN
HTTP/3	Miscellaneous
Cloudflare	CDN
Cloudflare Bot Management	Security
HSTS	Security

Web Application Vulnerabilities

Evidence

URL	Cookie Name	Evidence
https://phantom-sense-68c.notion.site/Top-Mistakes-New-Slot-Players-Make-1d58eecaa4e08004b794cec78329637a	notion_browser_id, notion_check_cookie_consent, notion_locale, NEXT_LOCALE	The server responded with Set-Cookie header(s) that does not specify the HttpOnly flag: Set-Cookie: notion_browser_id=11ca28bd-2c33-472b-92d0-cc04292ceb08 Set-Cookie: notion_check_cookie_consent=true Set-Cookie: notion_locale=en-US%2Fautodetect Set-Cookie: NEXT_LOCALE=en-US

Vulnerability description

We found that a cookie has been set without the HttpOnly flag, which means it can be accessed by potentially malicious JavaScript code running inside the web page. The root cause for this usually revolves around misconfigurations in the code or server settings.

Risk description

The risk is that an attacker who injects malicious JavaScript code on the page (e.g. by using an XSS attack) can access the cookie and can send it to another site. In case of a session cookie, this could lead to session hijacking.

Recommendation

Ensure that the HttpOnly flag is set for all cookies.

Classification

CWE	CWE-1004
OWASP Top 10 - 2017	A6 - Security Misconfiguration
OWASP Top 10 - 2021	A5 - Security Misconfiguration

Evidence

URL Evidence

URL	Evidence
https://phantom-sense-68c.notion.site/Top-Mistakes-New-Slot-Players-Make-1d58eecaa4e08004b794cec78329637a	Response headers include the HTTP Content-Security-Policy security header with the following security issues:script-src: 'self' can be problematic if you host JSONP, Angular or user uploaded files. default-src: The default-src directive should be set as a fall-back when other restrictions have not been specified. base-uri: Missing base-uri allows the injection of base tags. They can be used to set the base URL for all relative (script) URLs to an attacker controlled domain. We recommend setting it to 'none' or 'self'. script-src: ''unsafe-inline'' allows the execution of unsafe in-page scripts and event handlers. script-src: 'unsafe-eval' allows the execution of code injected into DOM APIs such as eval(). frame-ancestors: This directive tells the browser whether you want to allow your site to be framed or not. By preventing a browser from framing your site you can defend against attacks like clickjacking. The recommended value is 'none' or 'self'. object-src: Missing object-src allows the injection of plugins which can execute JavaScript. We recommend setting it to 'none'.

https://phantom-sense-68c.notion.site/Top-Mistakes-New-Slot-Players-Make-1d58eecaa4e08004b794cec78329637a

Response headers include the HTTP Content-Security-Policy security header with the following security issues:script-src: 'self' can be problematic if you host JSONP, Angular or user uploaded files. default-src: The default-src directive should be set as a fall-back when other restrictions have not been specified. base-uri: Missing base-uri allows the injection of base tags. They can be used to set the base URL for all relative (script) URLs to an attacker controlled domain. We recommend setting it to 'none' or 'self'. script-src: ''unsafe-inline'' allows the execution of unsafe in-page scripts and event handlers. script-src: 'unsafe-eval' allows the execution of code injected into DOM APIs such as eval(). frame-ancestors: This directive tells the browser whether you want to allow your site to be framed or not. By preventing a browser from framing your site you can defend against attacks like clickjacking. The recommended value is 'none' or 'self'. object-src: Missing object-src allows the injection of plugins which can execute JavaScript. We recommend setting it to 'none'.

Vulnerability description

We noticed that the Content-Security-Policy (CSP) header configured for the web application includes unsafe directives. The CSP header activates a protection mechanism implemented in web browsers which prevents exploitation of Cross-Site Scripting vulnerabilities (XSS) by restricting the sources from which content can be loaded or executed.

Risk description

For example, if the unsafe-inline directive is present in the CSP header, the execution of inline scripts and event handlers is allowed. This can be exploited by an attacker to execute arbitrary JavaScript code in the context of the vulnerable application.

Recommendation

Remove the unsafe values from the directives, adopt nonces or hashes for safer inclusion of inline scripts if they are needed, and explicitly define the sources from which scripts, styles, images or other resources can be loaded.

Classification

CWE	CWE-693
OWASP Top 10 - 2017	A6 - Security Misconfiguration
OWASP Top 10 - 2021	A5 - Security Misconfiguration

Evidence

Software / Version	Category
Amazon Web Services	PaaS
Amazon S3	CDN
HTTP/3	Miscellaneous
Cloudflare	CDN
Cloudflare Bot Management	Security
HSTS	Security

Vulnerability description

We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.

Risk description

The risk is that an attacker could use this information to mount specific attacks against the identified software type and version.

Recommendation

We recommend you to eliminate the information which permits the identification of software platform, technology, server and operating system: HTTP server headers, HTML meta information, etc.

Classification

OWASP Top 10 - 2017	A6 - Security Misconfiguration
OWASP Top 10 - 2021	A5 - Security Misconfiguration

Evidence

URL
https://phantom-sense-68c.notion.site/robots.txt

Vulnerability description

We found the robots.txt on the target server. This file instructs web crawlers what URLs and endpoints of the web application they can visit and crawl. Website administrators often misuse this file while attempting to hide some web pages from the users.

Risk description

There is no particular security risk in having a robots.txt file. However, it's important to note that adding endpoints in it should not be considered a security measure, as this file can be directly accessed and read by anyone.

Recommendation

We recommend you to manually review the entries from robots.txt and remove the ones which lead to sensitive locations in the website (ex. administration panels, configuration files, etc).

Classification

OWASP Top 10 - 2017	A6 - Security Misconfiguration
OWASP Top 10 - 2021	A5 - Security Misconfiguration

Evidence

URL	Method	Summary
https://phantom-sense-68c.notion.site/Top-Mistakes-New-Slot-Players-Make-1d58eecaa4e08004b794cec78329637a?pvs=4	OPTIONS	We did a HTTP OPTIONS request. The server responded with a 200 status code and the header: `Allow: GET,HEAD` Request / Response

Vulnerability description

We have noticed that the webserver responded with an Allow HTTP header when an OPTIONS HTTP request was sent. This method responds to requests by providing information about the methods available for the target resource.

Risk description

The only risk this might present nowadays is revealing debug HTTP methods that can be used on the server. This can present a danger if any of those methods can lead to sensitive information, like authentication information, secret keys.

Recommendation

We recommend that you check for unused HTTP methods or even better, disable the OPTIONS method. This can be done using your webserver configuration.

Classification

CWE	CWE-16
OWASP Top 10 - 2017	A6 - Security Misconfiguration
OWASP Top 10 - 2021	A5 - Security Misconfiguration

Infrastructure Vulnerabilities

Evidence

Domain Queried	DNS Record Type	Description	Value
phantom-sense-68c.notion.site	A	IPv4 address	208.103.161.33
phantom-sense-68c.notion.site	A	IPv4 address	208.103.161.32

Risk description

An initial step for an attacker aiming to learn about an organization involves conducting searches on its domain names to uncover DNS records associated with the organization. This strategy aims to amass comprehensive insights into the target domain, enabling the attacker to outline the organization's external digital landscape. This gathered intelligence may subsequently serve as a foundation for launching attacks, including those based on social engineering techniques. DNS records pointing to services or servers that are no longer in use can provide an attacker with an easy entry point into the network.

Recommendation

We recommend reviewing all DNS records associated with the domain and identifying and removing unused or obsolete records.

Evidence

Software / Version	Category
Amazon Web Services	PaaS
Cloudflare Bot Management	Security
Linkedin Ads	Advertising
HSTS	Security
Cloudflare	CDN
Amazon S3	CDN
HTTP/3	Miscellaneous

Vulnerability description

We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.

Risk description

The risk is that an attacker could use this information to mount specific attacks against the identified software type and version.

Recommendation

We recommend you to eliminate the information which permits the identification of software platform, technology, server and operating system: HTTP server headers, HTML meta information, etc.

Evidence

Software / Version	Category
Amazon Web Services	PaaS
Cloudflare Bot Management	Security
Linkedin Ads	Advertising
HSTS	Security
Cloudflare	CDN
Amazon S3	CDN
HTTP/3	Miscellaneous

Vulnerability description

We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.

Risk description

The risk is that an attacker could use this information to mount specific attacks against the identified software type and version.

Recommendation

We recommend you to eliminate the information which permits the identification of software platform, technology, server and operating system: HTTP server headers, HTML meta information, etc.

Evidence

Software / Version	Category
Cloudflare	CDN

Vulnerability description

We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.

Risk description

The risk is that an attacker could use this information to mount specific attacks against the identified software type and version.

Recommendation

We recommend you to eliminate the information which permits the identification of software platform, technology, server and operating system: HTTP server headers, HTML meta information, etc.