Vulnerability Scan Result

Target:

http://www.charmin.com/ (redirect)

Scanned target: https://www.charmin.com/en-us

Submitted: April 13, 2025 from AM

Public scan

Scan mode: Passive (non-intrusive)

Summary

low

Info

Low

Medium

High

Critical

Screenshot

Title:	Enjoy The Go With Best Toilet Paper Rolls & Flushable Wipes \| Charmin
Description:	Explore Charmin's toilet paper and flushable wet wipe products. Get toilet tissues for commercial and household purposes, save more with our coupons and offers.

IP Information

IP address	13.107.246.45
Country	US
AS number	AS8075
Net name	Microsoft Corporation

Open Ports

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

Web Technologies

Software / Version	Category
Azure	PaaS
Azure Front Door	Load balancers
crypto-js	JavaScript libraries
core-js 3.38.1	JavaScript libraries
Google Analytics	Analytics
Google Font API	Font scripts
Next.js 14.2.24	JavaScript frameworks, Web frameworks, Web servers, Static site generator
React	JavaScript frameworks
Webpack	Miscellaneous
Bazaarvoice Reviews	Reviews
Contentful	CMS
Google Tag Manager	Tag managers
HSTS	Security

Web Application Vulnerabilities

Evidence

URL	Evidence
https://www.charmin.com/en-us	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

URL	Evidence
https://www.charmin.com/en-us	Response headers include the HTTP Content-Security-Policy security header with the following security issues: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(). 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'. object-src: We recommend restricting object-src to 'none'. script-src: data: URI in script-src allows the execution of unsafe scripts. script-src: script-src should not allow '*' as source. This may enable execution of malicious JavaScript.

https://www.charmin.com/en-us

Response headers include the HTTP Content-Security-Policy security header with the following security issues: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(). 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'. object-src: We recommend restricting object-src to 'none'. script-src: data: URI in script-src allows the execution of unsafe scripts. script-src: script-src should not allow '*' as source. This may enable execution of malicious JavaScript.

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
Azure	PaaS
Azure Front Door	Load balancers
crypto-js	JavaScript libraries
core-js 3.38.1	JavaScript libraries
Google Analytics	Analytics
Google Font API	Font scripts
Next.js 14.2.24	JavaScript frameworks, Web frameworks, Web servers, Static site generator
React	JavaScript frameworks
Webpack	Miscellaneous
Bazaarvoice Reviews	Reviews
Contentful	CMS
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.

Classification

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

Evidence

URL
https://www.charmin.com/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

Infrastructure Vulnerabilities

Evidence

Domain Queried	DNS Record Type	Description	Value
www.charmin.com	A	IPv4 address	13.107.246.45
www.charmin.com	AAAA	IPv6 address	2620:1ec:bdf::45
www.charmin.com	CNAME	Canonical name	charmin-com-01-dtbmetg7dbdbd0da.a02.azurefd.net

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.