Vulnerability Scan Result

Target:

https://f7cnp-eqaaa-aaaad-qfm6q-cai.icp0.io/blog/qold-a-to-z/index.html

Scanned target: https://f7cnp-eqaaa-aaaad-qfm6q-cai.icp0.io/blog/qold-a-to-z/index.html

Submitted: April 14, 2025 from NO

Public scan

Scan mode: Passive (non-intrusive)

Summary

medium

Info

Low

Medium

High

Critical

Screenshot

https://f7cnp-eqaaa-aaaad-qfm6q-cai.icp0.io/blog/qold-a-to-z/index.html

Title:	Qold: A to Z \| Whitesmith
Description:	For over a decade, we’ve been collaborating with our clients to help them build digital products that bring effective change to people and society.

IP Information

IP address	212.71.124.187
Country	CH
AS number	AS24951
Net name	Everyware Ag

IP address	212.71.124.186
Country	CH
AS number	AS24951
Net name	Everyware Ag

IP address	193.118.59.140
Country	GB
AS number	AS21859
Net name	Zenlayer Inc

Open Ports

80/tcp	http	- -
443/tcp	https	- -

Web Technologies

Software / Version	Category
Google Hosted Libraries	CDN
Google Analytics UA	Analytics
jQuery 1.11.3	JavaScript libraries
MailChimp	Marketing automation, Email
HSTS	Security

Web Application Vulnerabilities

Evidence

CVSS	CVE	Summary	Affected software
4.3	CVE-2015-9251	jQuery before 3.0.0 is vulnerable to Cross-site Scripting (XSS) attacks when a cross-domain Ajax request is performed without the dataType option, causing text/javascript responses to be executed.	jquery 1.11.3
4.3	CVE-2019-11358	jQuery before 3.4.0, as used in Drupal, Backdrop CMS, and other products, mishandles jQuery.extend(true, {}, ...) because of Object.prototype pollution. If an unsanitized source object contained an enumerable __proto__ property, it could extend the native Object.prototype.	jquery 1.11.3
4.3	CVE-2020-11023	In jQuery versions greater than or equal to 1.0.3 and before 3.5.0, passing HTML containing <option> elements from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0.	jquery 1.11.3
4.3	CVE-2020-11022	In jQuery versions greater than or equal to 1.2 and before 3.5.0, passing HTML from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0.	jquery 1.11.3

Vulnerability description

We noticed known vulnerabilities in the target application based on the server responses. They are usually related to outdated systems and expose the affected applications to the risk of unauthorized access to confidential data and possibly denial of service attacks. Depending on the system distribution the affected software can be patched but displays the same version, requiring manual checking.

Risk description

The risk is that an attacker could search for an appropriate exploit (or create one himself) for any of these vulnerabilities and use it to attack the system.

Recommendation

In order to eliminate the risk of these vulnerabilities, we recommend you check the installed software version and upgrade to the latest version.

Classification

CWE	CWE-1026
OWASP Top 10 - 2017	A9 - Using Components with Known Vulnerabilities
OWASP Top 10 - 2021	A6 - Vulnerable and Outdated Components

Evidence

URL	Evidence
https://f7cnp-eqaaa-aaaad-qfm6q-cai.icp0.io/blog/qold-a-to-z/index.html	Response headers do not include the Referrer-Policy HTTP security header as well as the `<meta/>` tag with name 'referrer' is not present in the response.

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://f7cnp-eqaaa-aaaad-qfm6q-cai.icp0.io/blog/qold-a-to-z/index.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	A6 - Security Misconfiguration
OWASP Top 10 - 2021	A5 - Security Misconfiguration

Evidence

URL	Evidence
https://f7cnp-eqaaa-aaaad-qfm6q-cai.icp0.io/blog/qold-a-to-z/index.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	A6 - Security Misconfiguration
OWASP Top 10 - 2021	A5 - Security Misconfiguration

Evidence

Software / Version	Category
Google Hosted Libraries	CDN
Google Analytics UA	Analytics
jQuery 1.11.3	JavaScript libraries
MailChimp	Marketing automation, Email
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://f7cnp-eqaaa-aaaad-qfm6q-cai.icp0.io/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://f7cnp-eqaaa-aaaad-qfm6q-cai.icp0.io/blog/qold-a-to-z/index.html	OPTIONS	We did a HTTP OPTIONS request. The server responded with a 200 status code and the header: `Allow: POST,GET,HEAD,PUT,DELETE,PATCH` 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
f7cnp-eqaaa-aaaad-qfm6q-cai.icp0.io	A	IPv4 address	212.71.124.187
f7cnp-eqaaa-aaaad-qfm6q-cai.icp0.io	A	IPv4 address	193.118.59.140
f7cnp-eqaaa-aaaad-qfm6q-cai.icp0.io	A	IPv4 address	212.71.124.186
f7cnp-eqaaa-aaaad-qfm6q-cai.icp0.io	NS	Name server	hassan.ns.cloudflare.com
f7cnp-eqaaa-aaaad-qfm6q-cai.icp0.io	NS	Name server	lara.ns.cloudflare.com
f7cnp-eqaaa-aaaad-qfm6q-cai.icp0.io	SOA	Start of Authority	hassan.ns.cloudflare.com. dns.cloudflare.com. 2369781486 10000 2400 604800 1800
f7cnp-eqaaa-aaaad-qfm6q-cai.icp0.io	AAAA	IPv6 address	2a0b:21c0:4003:2:5000:55ff:feb8:5f89
f7cnp-eqaaa-aaaad-qfm6q-cai.icp0.io	AAAA	IPv6 address	2a00:fb01:400:200:5000:5aff:fef2:9428
f7cnp-eqaaa-aaaad-qfm6q-cai.icp0.io	AAAA	IPv6 address	2a00:fb01:400:200:5000:eeff:fe3d:aa0d
f7cnp-eqaaa-aaaad-qfm6q-cai.icp0.io	SPF	Sender Policy Framework	"v=spf1 -all"
f7cnp-eqaaa-aaaad-qfm6q-cai.icp0.io	CAA	Certificate Authority Authorization	0 issue "comodoca.com"
f7cnp-eqaaa-aaaad-qfm6q-cai.icp0.io	CAA	Certificate Authority Authorization	0 issue "digicert.com; cansignhttpexchanges=yes"
f7cnp-eqaaa-aaaad-qfm6q-cai.icp0.io	CAA	Certificate Authority Authorization	0 issue "letsencrypt.org"
f7cnp-eqaaa-aaaad-qfm6q-cai.icp0.io	CAA	Certificate Authority Authorization	0 issue "pki.goog; cansignhttpexchanges=yes"
f7cnp-eqaaa-aaaad-qfm6q-cai.icp0.io	CAA	Certificate Authority Authorization	0 issue "ssl.com"
f7cnp-eqaaa-aaaad-qfm6q-cai.icp0.io	CAA	Certificate Authority Authorization	0 issuewild "comodoca.com"
f7cnp-eqaaa-aaaad-qfm6q-cai.icp0.io	CAA	Certificate Authority Authorization	0 issuewild "digicert.com; cansignhttpexchanges=yes"
f7cnp-eqaaa-aaaad-qfm6q-cai.icp0.io	CAA	Certificate Authority Authorization	0 issuewild "letsencrypt.org"
f7cnp-eqaaa-aaaad-qfm6q-cai.icp0.io	CAA	Certificate Authority Authorization	0 issuewild "pki.goog; cansignhttpexchanges=yes"
f7cnp-eqaaa-aaaad-qfm6q-cai.icp0.io	CAA	Certificate Authority Authorization	0 issuewild "ssl.com"
f7cnp-eqaaa-aaaad-qfm6q-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.