Vulnerability Scan Result
| Title: | Pokemon Awakening |
| Description: | No description found |
| IP address | 185.199.108.153 |
| Country | US  |
| AS number | AS54113 |
| Net name | Fastly Inc |
| IP address | 185.199.109.153 |
| Country | US |
| AS number | AS54113 |
| Net name | Fastly Inc |
| IP address | 185.199.110.153 |
| Country | US |
| AS number | AS54113 |
| Net name | Fastly Inc |
| IP address | 185.199.111.153 |
| Country | US |
| AS number | AS54113 |
| Net name | Fastly Inc |
80/tcp | http | GitHub.com - |
443/tcp | https | GitHub.com - |
| Software / Version | Category |
|---|---|
| Google Analytics GA4 | Analytics |
| GitHub Pages | PaaS |
| Sectigo | SSL/TLS certificate authorities |
| Fastly | CDN |
| Google Tag Manager | Tag managers |
| jsDelivr | CDN |
| HSTS | Security |
| Varnish | Caching |
Web Application Vulnerabilities
Evidence
| URL | Evidence |
|---|---|
| https://kidfates.github.io/ | Response does not include the HTTP Content-Security-Policy security header or meta tag |
Vulnerability description
We noticed that the target application lacks the Content-Security-Policy (CSP) header in its HTTP responses. The CSP header is a security measure that instructs web browsers to enforce specific security rules, effectively preventing the exploitation of Cross-Site Scripting (XSS) vulnerabilities.
Risk description
The risk is that if the target application is vulnerable to XSS, lack of this header makes it easily exploitable by attackers.
Recommendation
Configure the Content-Security-Header to be sent with each HTTP response in order to apply the specific policies needed by the application.
Classification
| CWE | CWE-693 |
| OWASP Top 10 - 2017 | A6 - Security Misconfiguration |
| OWASP Top 10 - 2021 | A5 - Security Misconfiguration |
Evidence
| URL | Evidence |
|---|---|
| https://kidfates.github.io/ | Response headers do not include the Referrer-Policy HTTP security header as well as the |
Vulnerability description
We noticed that the target application's server responses lack the Referrer-Policy HTTP header, which controls how much referrer information the browser will send with each request originated from the current web application.
Risk description
The risk is that if a user visits a web page (e.g. "http://example.com/pricing/") and clicks on a link from that page going to e.g. "https://www.google.com", the browser will send to Google the full originating URL in the `Referer` header, assuming the Referrer-Policy header is not set. The originating URL could be considered sensitive information and it could be used for user tracking.
Recommendation
The Referrer-Policy header should be configured on the server side to avoid user tracking and inadvertent information leakage. The value `no-referrer` of this header instructs the browser to omit the Referer header entirely.
Classification
| CWE | CWE-693 |
| OWASP Top 10 - 2017 | A6 - Security Misconfiguration |
| OWASP Top 10 - 2021 | A5 - Security Misconfiguration |
Evidence
| URL | Evidence |
|---|---|
| https://kidfates.github.io/ | Response headers do not include the X-Content-Type-Options HTTP security header |
Vulnerability description
We noticed that the target application's server responses lack the X-Content-Type-Options header. This header is particularly important for preventing Internet Explorer from reinterpreting the content of a web page (MIME-sniffing) and thus overriding the value of the Content-Type header.
Risk description
The risk is that lack of this header could make possible attacks such as Cross-Site Scripting or phishing in Internet Explorer browsers.
Recommendation
We recommend setting the X-Content-Type-Options header such as `X-Content-Type-Options: nosniff`.
Classification
| CWE | CWE-693 |
| OWASP Top 10 - 2017 | A6 - Security Misconfiguration |
| OWASP Top 10 - 2021 | A5 - Security Misconfiguration |
Evidence
| URL | Evidence |
|---|---|
| https://kidfates.github.io/'' | Response headers include the HTTP Content-Security-Policy security header with the following security issues: |
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 |
|---|---|
| Google Analytics GA4 | Analytics |
| GitHub Pages | PaaS |
| Sectigo | SSL/TLS certificate authorities |
| Fastly | CDN |
| Google Tag Manager | Tag managers |
| jsDelivr | CDN |
| HSTS | Security |
| Varnish | Caching |
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
Vulnerability description
Website is accessible.
Vulnerability description
We have noticed that the server is missing the security.txt file, which is considered a good practice for web security. It provides a standardized way for security researchers and the public to report security vulnerabilities or concerns by outlining the preferred method of contact and reporting procedures.
Risk description
There is no particular risk in not having a security.txt file for your server. However, this file is important because it offers a designated channel for reporting vulnerabilities and security issues.
Recommendation
We recommend you to implement the security.txt file according to the standard, in order to allow researchers or users report any security issues they find, improving the defensive mechanisms of your server.
Classification
| OWASP Top 10 - 2017 | A6 - Security Misconfiguration |
| OWASP Top 10 - 2021 | A5 - Security Misconfiguration |
Infrastructure Vulnerabilities
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| kidfates.github.io | A | IPv4 address | 185.199.108.153 |
| kidfates.github.io | A | IPv4 address | 185.199.109.153 |
| kidfates.github.io | A | IPv4 address | 185.199.110.153 |
| kidfates.github.io | A | IPv4 address | 185.199.111.153 |
| kidfates.github.io | AAAA | IPv6 address | 2606:50c0:8000::153 |
| kidfates.github.io | AAAA | IPv6 address | 2606:50c0:8001::153 |
| kidfates.github.io | AAAA | IPv6 address | 2606:50c0:8002::153 |
| kidfates.github.io | AAAA | IPv6 address | 2606:50c0:8003::153 |
| kidfates.github.io | CAA | Certificate Authority Authorization | 0 issue "digicert.com" |
| kidfates.github.io | CAA | Certificate Authority Authorization | 0 issue "letsencrypt.org" |
| kidfates.github.io | CAA | Certificate Authority Authorization | 0 issue "sectigo.com" |
| kidfates.github.io | CAA | Certificate Authority Authorization | 0 issuewild "digicert.com" |
| kidfates.github.io | CAA | Certificate Authority Authorization | 0 issuewild "sectigo.com" |
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
Vulnerability description
OS detection couldn't determine the operating system.
Evidence
We managed to detect the redirect using the following Request / Response chain.
Recommendation
Vulnerability checks are skipped for ports that redirect to another port. We recommend scanning the redirected port directly.
Evidence
| Software / Version | Category |
|---|---|
| Varnish | Caching |
| GitHub Pages | PaaS |
| jsDelivr | CDN |
| Google Tag Manager | Tag managers |
| Google Analytics GA4 | Analytics |
| Sectigo | SSL/TLS certificate authorities |
| HSTS | Security |
| Fastly | 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.