Vulnerability Scan Result
| Title: | SUSHI |
| Description: | Be a DeFi Chef with Sushi. Swap, earn, stack yields, lend, borrow, leverage all on one decentralized, community driven platform. Welcome home to DeFi |
| ip_address | 195.5.171.242 |
| country | US  |
| network_name | Trenka Informatik Ag |
| asn | AS29655 |
| ip_address | 212.71.124.188 |
| country | CH  |
| network_name | Everyware Ag |
| asn | AS24951 |
80/tcp | http | - - |
443/tcp | https | - - |
| Software / Version | Category |
|---|---|
| Ethers | JavaScript libraries |
| web-vitals | JavaScript libraries, RUM |
| core-js 2.6.5 | JavaScript libraries |
| Google Analytics | Analytics |
| Next.js 12.0.4 | JavaScript frameworks, Web frameworks, Web servers, Static site generator |
| Open Graph | Miscellaneous |
| React | JavaScript frameworks |
| Sentry | Issue trackers |
| styled-components 5.3.3 | JavaScript frameworks, Development |
| PWA | Miscellaneous |
| Webpack | Miscellaneous |
| Google Tag Manager | Tag managers |
| HSTS | Security |
Web Application Vulnerabilities
Evidence
| URL | Evidence |
|---|---|
| https://aufz7-4qaaa-aaaaf-qae3a-cai.icp0.io/user/balances.html | 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 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Evidence |
|---|---|
| https://aufz7-4qaaa-aaaaf-qae3a-cai.icp0.io/user/balances.html | 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 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Evidence |
|---|---|
| https://aufz7-4qaaa-aaaaf-qae3a-cai.icp0.io/user/balances.html | 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 | |
| OWASP Top 10 - 2021 |
Evidence
| Software / Version | Category |
|---|---|
| Ethers | JavaScript libraries |
| web-vitals | JavaScript libraries, RUM |
| core-js 2.6.5 | JavaScript libraries |
| Google Analytics | Analytics |
| Next.js 12.0.4 | JavaScript frameworks, Web frameworks, Web servers, Static site generator |
| Open Graph | Miscellaneous |
| React | JavaScript frameworks |
| Sentry | Issue trackers |
| styled-components 5.3.3 | JavaScript frameworks, Development |
| PWA | Miscellaneous |
| 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
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| aufz7-4qaaa-aaaaf-qae3a-cai.icp0.io | A | IPv4 address | 212.71.124.188 |
| aufz7-4qaaa-aaaaf-qae3a-cai.icp0.io | A | IPv4 address | 195.5.171.242 |
| aufz7-4qaaa-aaaaf-qae3a-cai.icp0.io | NS | Name server | hassan.ns.cloudflare.com |
| aufz7-4qaaa-aaaaf-qae3a-cai.icp0.io | NS | Name server | lara.ns.cloudflare.com |
| aufz7-4qaaa-aaaaf-qae3a-cai.icp0.io | SOA | Start of Authority | hassan.ns.cloudflare.com. dns.cloudflare.com. 2385397912 10000 2400 604800 1800 |
| aufz7-4qaaa-aaaaf-qae3a-cai.icp0.io | AAAA | IPv6 address | 2602:fb2b:110:1:bcfb:b8ff:fe09:c741 |
| aufz7-4qaaa-aaaaf-qae3a-cai.icp0.io | AAAA | IPv6 address | 2a00:fb01:400:200:5000:61ff:fe45:43ab |
| aufz7-4qaaa-aaaaf-qae3a-cai.icp0.io | SPF | Sender Policy Framework | "v=spf1 -all" |
| aufz7-4qaaa-aaaaf-qae3a-cai.icp0.io | CAA | Certificate Authority Authorization | 0 issue "comodoca.com" |
| aufz7-4qaaa-aaaaf-qae3a-cai.icp0.io | CAA | Certificate Authority Authorization | 0 issue "digicert.com; cansignhttpexchanges=yes" |
| aufz7-4qaaa-aaaaf-qae3a-cai.icp0.io | CAA | Certificate Authority Authorization | 0 issue "letsencrypt.org" |
| aufz7-4qaaa-aaaaf-qae3a-cai.icp0.io | CAA | Certificate Authority Authorization | 0 issue "pki.goog; cansignhttpexchanges=yes" |
| aufz7-4qaaa-aaaaf-qae3a-cai.icp0.io | CAA | Certificate Authority Authorization | 0 issue "ssl.com" |
| aufz7-4qaaa-aaaaf-qae3a-cai.icp0.io | CAA | Certificate Authority Authorization | 0 issuewild "comodoca.com" |
| aufz7-4qaaa-aaaaf-qae3a-cai.icp0.io | CAA | Certificate Authority Authorization | 0 issuewild "digicert.com; cansignhttpexchanges=yes" |
| aufz7-4qaaa-aaaaf-qae3a-cai.icp0.io | CAA | Certificate Authority Authorization | 0 issuewild "letsencrypt.org" |
| aufz7-4qaaa-aaaaf-qae3a-cai.icp0.io | CAA | Certificate Authority Authorization | 0 issuewild "pki.goog; cansignhttpexchanges=yes" |
| aufz7-4qaaa-aaaaf-qae3a-cai.icp0.io | CAA | Certificate Authority Authorization | 0 issuewild "ssl.com" |
| aufz7-4qaaa-aaaaf-qae3a-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.
Evidence
| Operating System | Accuracy |
|---|---|
| Linux 3.4 | 86% |
Vulnerability description
OS Detection
Evidence
| Software / Version | Category |
|---|---|
| styled-components 5.3.3 | JavaScript frameworks, Development |
| React | JavaScript frameworks |
| Google Analytics | Analytics |
| web-vitals | JavaScript libraries, RUM |
| HSTS | Security |
| PWA | Miscellaneous |
| Open Graph | 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.