Vulnerability Scan Result
| Title: | ICP Tokens by Market Cap |
| Description: | Explore ICP Tokens for real-time market data, portfolio management, and token analysis within the Internet Computer ecosystem. Stay updated with top ICP projects |
| ip_address | 212.71.124.188 |
| country | CH  |
| network_name | Everyware Ag |
| asn | AS24951 |
| ip_address | 195.5.171.242 |
| country | US  |
| network_name | Trenka Informatik Ag |
| asn | AS29655 |
80/tcp | http | - - |
443/tcp | https | - - |
| Software / Version | Category |
|---|---|
| Emotion | JavaScript frameworks, Development |
| Google Analytics | Analytics |
| Google Font API | Font scripts |
| MUI | UI frameworks |
| Next.js 13.5.7 | JavaScript frameworks, Web frameworks, Web servers, Static site generator |
| React | JavaScript frameworks |
| Tally | Surveys |
| Webpack | Miscellaneous |
| Google Tag Manager | Tag managers |
| HSTS | Security |
Web Application Vulnerabilities
Evidence
| URL | Evidence |
|---|---|
| https://id2dc-kiaaa-aaaag-augwq-cai.icp0.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 | |
| OWASP Top 10 - 2021 |
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).
Evidence
| Software / Version | Category |
|---|---|
| Emotion | JavaScript frameworks, Development |
| Google Analytics | Analytics |
| Google Font API | Font scripts |
| MUI | UI frameworks |
| Next.js 13.5.7 | JavaScript frameworks, Web frameworks, Web servers, Static site generator |
| React | JavaScript frameworks |
| Tally | Surveys |
| Webpack | Miscellaneous |
| Google Tag Manager | Tag managers |
| 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.
Evidence
Vulnerability description
Website is accessible.
Infrastructure Vulnerabilities
Evidence
We found insecure DNS cookie usage on the following nameservers: hassan.ns.cloudflare.com, lara.ns.cloudflare.com
Vulnerability description
We found that the server does not implement DNS Cookies or uses them insecurely. DNS Cookies help prevent DNS-based attacks, such as spoofing and amplification attacks.
Risk description
The risk exists because without DNS Cookies, the server is vulnerable to DNS spoofing and amplification attacks. Attackers can manipulate responses or use the server in distributed denial-of-service (DDoS) attacks, compromising network availability and security.
Recommendation
We recommend enabling DNS Cookies to prevent spoofed DNS responses. Ensure proper cookie validation is implemented to mitigate DNS amplification attacks. Regularly update DNS servers to support the latest DNS security features.
Evidence
| Operating System | Accuracy |
|---|---|
| Linux 3.4 | 86% |
Vulnerability description
OS Detection
Evidence
| Software / Version | Category |
|---|---|
| HSTS | Security |
| Google Analytics | Analytics |
| Google Tag Manager | Tag managers |
| Tally | Surveys |
| Google Font API | Font scripts |
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
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| id2dc-kiaaa-aaaag-augwq-cai.icp0.io | A | IPv4 address | 212.71.124.188 |
| id2dc-kiaaa-aaaag-augwq-cai.icp0.io | A | IPv4 address | 195.5.171.242 |
| id2dc-kiaaa-aaaag-augwq-cai.icp0.io | NS | Name server | hassan.ns.cloudflare.com |
| id2dc-kiaaa-aaaag-augwq-cai.icp0.io | NS | Name server | lara.ns.cloudflare.com |
| id2dc-kiaaa-aaaag-augwq-cai.icp0.io | SOA | Start of Authority | hassan.ns.cloudflare.com. dns.cloudflare.com. 2388940957 10000 2400 604800 1800 |
| id2dc-kiaaa-aaaag-augwq-cai.icp0.io | AAAA | IPv6 address | 2a00:fb01:400:200:5000:61ff:fe45:43ab |
| id2dc-kiaaa-aaaag-augwq-cai.icp0.io | AAAA | IPv6 address | 2602:fb2b:110:1:bcfb:b8ff:fe09:c741 |
| id2dc-kiaaa-aaaag-augwq-cai.icp0.io | SPF | Sender Policy Framework | "v=spf1 -all" |
| id2dc-kiaaa-aaaag-augwq-cai.icp0.io | CAA | Certificate Authority Authorization | 0 issue "comodoca.com" |
| id2dc-kiaaa-aaaag-augwq-cai.icp0.io | CAA | Certificate Authority Authorization | 0 issue "digicert.com; cansignhttpexchanges=yes" |
| id2dc-kiaaa-aaaag-augwq-cai.icp0.io | CAA | Certificate Authority Authorization | 0 issue "letsencrypt.org" |
| id2dc-kiaaa-aaaag-augwq-cai.icp0.io | CAA | Certificate Authority Authorization | 0 issue "pki.goog; cansignhttpexchanges=yes" |
| id2dc-kiaaa-aaaag-augwq-cai.icp0.io | CAA | Certificate Authority Authorization | 0 issue "ssl.com" |
| id2dc-kiaaa-aaaag-augwq-cai.icp0.io | CAA | Certificate Authority Authorization | 0 issuewild "comodoca.com" |
| id2dc-kiaaa-aaaag-augwq-cai.icp0.io | CAA | Certificate Authority Authorization | 0 issuewild "digicert.com; cansignhttpexchanges=yes" |
| id2dc-kiaaa-aaaag-augwq-cai.icp0.io | CAA | Certificate Authority Authorization | 0 issuewild "letsencrypt.org" |
| id2dc-kiaaa-aaaag-augwq-cai.icp0.io | CAA | Certificate Authority Authorization | 0 issuewild "pki.goog; cansignhttpexchanges=yes" |
| id2dc-kiaaa-aaaag-augwq-cai.icp0.io | CAA | Certificate Authority Authorization | 0 issuewild "ssl.com" |
| id2dc-kiaaa-aaaag-augwq-cai.icp0.io | CNAME | Canonical name | boundary.dfinity.network |
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.