Vulnerability Scan Result
| Title: | Logo Canvas Tote — Comfrt |
| Description: | Experience the perfect blend of practicality, durability, and style. The perfect weekend tote has arrived. Detailed with the Comfrt logo on the strap in black. |
| ip_address | 104.18.27.149 |
| country | - |
| network_name | Cloudflare Inc |
| asn | AS13335 |
| ip_address | 104.18.26.149 |
| country | - |
| network_name | Cloudflare Inc |
| asn | AS13335 |
80/tcp | http | Cloudflare http proxy - |
443/tcp | https | cloudflare - |
2082/tcp | http | Cloudflare http proxy - |
2083/tcp | https | nginx - |
2086/tcp | http | Cloudflare http proxy - |
2087/tcp | https | nginx - |
8080/tcp | http | Cloudflare http proxy - |
8443/tcp | http | cloudflare - |
No technologies could be detected.
Web Application Vulnerabilities
Evidence
| URL | Cookie Name | Evidence |
|---|---|---|
| https://comfrt.com/products/logo-canvas-tote.oembed | localization, cart_currency, _shopify_y, _shopify_s | The server responded with Set-Cookie header(s) that does not specify the HttpOnly flag: Set-Cookie: localization=US Set-Cookie: cart_currency=USD Set-Cookie: _shopify_y=342661d5-4e02-40e6-9a6d-3c4c22510a40 Set-Cookie: _shopify_s=069be59a-6d26-430e-bd4d-6bdfdbae0ec1 |
Vulnerability description
We found that a cookie has been set without the HttpOnly flag, which means it can be accessed by potentially malicious JavaScript code running inside the web page. The root cause for this usually revolves around misconfigurations in the code or server settings.
Risk description
The risk is that an attacker who injects malicious JavaScript code on the page (e.g. by using an XSS attack) can access the cookie and can send it to another site. In case of a session cookie, this could lead to session hijacking.
Recommendation
Ensure that the HttpOnly flag is set for all cookies.
Classification
| CWE | CWE-1004 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Cookie Name | Evidence |
|---|---|---|
| https://comfrt.com/products/logo-canvas-tote | __orly_aid, _landing_page, _shopify_sa_p | Set-Cookie: __orly_aid=9QjkjMuUguAlg9Na8MY1l7uf4-9QcHD7WzHf-v2 Set-Cookie: _landing_page=%2Fproducts%2Flogo-canvas-tote Set-Cookie: _shopify_sa_p= |
Vulnerability description
We found that a cookie has been set without the Secure flag, which means the browser will send it over an unencrypted channel (plain HTTP) if such a request is made. The root cause for this usually revolves around misconfigurations in the code or server settings.
Risk description
The risk exists that an attacker will intercept the clear-text communication between the browser and the server and he will steal the cookie of the user. If this is a session cookie, the attacker could gain unauthorized access to the victim's web session.
Recommendation
Whenever a cookie contains sensitive information or is a session token, then it should always be passed using an encrypted channel. Ensure that the secure flag is set for cookies containing such sensitive information.
Classification
| CWE | CWE-614 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Cookie Name | Evidence |
|---|---|---|
| https://comfrt.com/products/logo-canvas-tote | __orly_aid | Set-Cookie: .comfrt.com |
Vulnerability description
We found that the target application sets cookies with a domain scope that is too broad. Specifically, cookies intended for use within a particular application are configured in such a way that they can be accessed by multiple subdomains of the same primary domain.
Risk description
The risk is that a cookie set for example.com may be sent along with the requests sent to dev.example.com, calendar.example.com, hostedsite.example.com. Potentially risky websites under your main domain may access those cookies and use the victim session from the main site.
Recommendation
The `Domain` attribute should be set to the origin host to limit the scope to that particular server. For example if the application resides on server app.mysite.com, then it should be set to `Domain=app.mysite.com`
Classification
| CWE | CWE-614 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
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
| URL | Evidence |
|---|---|
| https://comfrt.com/products/logo-canvas-tote | 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://comfrt.com/products/logo-canvas-tote | Response headers do not include the HTTP Strict-Transport-Security header |
Vulnerability description
We noticed that the target application lacks the HTTP Strict-Transport-Security header in its responses. This security header is crucial as it instructs browsers to only establish secure (HTTPS) connections with the web server and reject any HTTP connections.
Risk description
The risk is that lack of this header permits an attacker to force a victim user to initiate a clear-text HTTP connection to the server, thus opening the possibility to eavesdrop on the network traffic and extract sensitive information (e.g. session cookies).
Recommendation
The Strict-Transport-Security HTTP header should be sent with each HTTPS response. The syntax is as follows: `Strict-Transport-Security: max-age=<seconds>[; includeSubDomains]` The parameter `max-age` gives the time frame for requirement of HTTPS in seconds and should be chosen quite high, e.g. several months. A value below 7776000 is considered as too low by this scanner check. The flag `includeSubDomains` defines that the policy applies also for sub domains of the sender of the response.
Classification
| CWE | CWE-693 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Evidence |
|---|---|
| https://comfrt.com/products/logo-canvas-tote | 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
| URL | Evidence |
|---|---|
| https://comfrt.com/products/logo-canvas-tote | 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
Vulnerability description
Website is accessible.
Evidence
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.
Infrastructure Vulnerabilities
Evidence
We found insecure DNS cookie usage on the following nameservers: heather.ns.cloudflare.com, joel.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 |
|---|---|---|---|
| _dmarc.comfrt.com | TXT | Text record | "v=DMARC1; p=quarantine; pct=100; rua=mailto:dmarc@comfrt.com;" |
Vulnerability description
We found that the DMARC record for the domain is not configured with sp policy, meaning that no policy is enforced for subdomains. When a DMARC record does not include a subdomain policy (sp directive), subdomains are not explicitly covered by the main domain's DMARC policy. This means that emails sent from subdomains (e.g., sub.example.com) may not be subject to the same DMARC enforcement as the main domain (example.com). As a result, attackers could potentially spoof emails from subdomains without being blocked or flagged, even if the main domain has a strict DMARC policy.
Risk description
Without a subdomain policy (sp directive) in the DMARC record, subdomains are not protected by the same DMARC enforcement as the main domain, leaving them vulnerable to spoofing attacks. This inconsistency can be exploited by attackers to send phishing emails from subdomains, undermining the organization’s overall email security.
Recommendation
To mitigate the risk, we recommend configuring the DMARC record with a subdomain policy by adding the sp=reject or sp=quarantine directive. This will extend DMARC enforcement to all subdomains, preventing spoofing attempts and maintaining consistent security across both the main domain and its subdomains.
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| _dmarc.comfrt.com | TXT | Text record | "v=DMARC1; p=quarantine; pct=100; rua=mailto:dmarc@comfrt.com;" |
Vulnerability description
We found that the DMARC record for the domain is not configured with ruf tag. A missing ruf (forensic reporting) tag in a DMARC record indicates that the domain owner has not enabled the collection of detailed failure reports. Forensic reports provide valuable insights into specific instances where emails fail DMARC authentication. Without the ruf tag, the domain administrator loses the ability to receive and analyze these reports, making it difficult to investigate individual email failures or identify targeted phishing or spoofing attacks that may be exploiting weaknesses in the email authentication setup.
Risk description
Without forensic reports (ruf), domain owners have limited visibility into the specifics of failed DMARC validation. This means potential malicious activity, such as email spoofing or phishing attempts, might go unnoticed until they result in more significant security breaches or reputational damage. Forensic reports allow for quick response to email abuses by providing detailed information about the failure, including the header information of the emails involved. The absence of this data hampers an organization's ability to identify and mitigate threats targeting its domain, increasing the risk of ongoing spoofing and fraud.
Recommendation
We recommend configuring the ruf tag in the DMARC record. This tag specifies where forensic reports should be sent, providing the domain owner with detailed data on DMARC validation failures. Forensic reports allow administrators to analyze why certain emails failed authentication, making it easier to fine-tune DMARC policies or address potential vulnerabilities. Ensure that the ruf email address belongs to a secure and trusted location capable of handling sensitive email data.
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| _dmarc.comfrt.com | TXT | Text record | "v=DMARC1; p=quarantine; pct=100; rua=mailto:dmarc@comfrt.com;" |
Vulnerability description
We found that the target uses p=quarantine in the DMARC policy. When a DMARC policy is set to p=quarantine, emails that fail DMARC validation are delivered but placed in the recipient’s spam or junk folder. Although it offers some protection, this policy is less strict than p=reject, which blocks such emails entirely.
Risk description
While emails failing DMARC validation are sent to the spam folder, users may still retrieve them from there, leading to a higher risk of phishing and spoofing attacks succeeding. Moreover, less strict enforcement may allow more fraudulent emails to reach user inboxes if misclassified.
Recommendation
We recommend considering moving to a stricter policy, such as p=reject, where emails that fail DMARC validation are completely rejected rather than delivered to spam folders. This reduces the risk of users interacting with potentially malicious emails.
Evidence
| Software / Version | Category |
|---|---|
| Shopify | Ecommerce |
| Pinterest Ads | Advertising |
| LiveIntent | Email, Advertising |
| Cloudflare | CDN |
| Northbeam | Analytics |
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
| Operating System | Accuracy |
|---|---|
| FreeBSD 11.1-STABLE | 91% |
Vulnerability description
OS Detection
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| comfrt.com | SPF | Sender Policy Framework | "v=spf1 include:secureserver.net include:_spf.google.com include:mail.zendesk.com -all" |
Evidence
| DKIM selector | Key type | Key size | Value |
|---|---|---|---|
| rsa | 1422 | "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA23my65M5MnelJUeml6Efw6N5bUyh095lTiE+A8PpMpasbk+wXFdPiP0BoM2pHGg5IbYL41LGpJ40U8OC+gVyW1PNUWpPw+PA87/Tlx84PGFIA+qzAaxvXlvMEAEuz7iQnSJ2tdm43Nb4+wkxKNu2Q29aMHO+YmzalsZkiSHpbYA869z3QQaRmBBZdtkcolvs1" "DevqGU9DbLnlyUufBALG5VEMP5l/1EQeB+lzdLgNzLDy5EylbSzCt8LQ0wRQ1woIdJX67YXOBz+DJDzx/X+ODG3ASyi+JQC2HUkesy18Hu1FWlOwdn8wwBkyJDEmLgtpSFHTqBnf/5mY3r4hnkA3wIDAQAB" |
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| comfrt.com | A | IPv4 address | 104.18.26.149 |
| comfrt.com | A | IPv4 address | 104.18.27.149 |
| comfrt.com | NS | Name server | heather.ns.cloudflare.com |
| comfrt.com | NS | Name server | joel.ns.cloudflare.com |
| comfrt.com | MX | Mail server | 0 smtp.google.com |
| comfrt.com | SOA | Start of Authority | heather.ns.cloudflare.com. dns.cloudflare.com. 2385274043 10000 2400 604800 1800 |
| comfrt.com | AAAA | IPv6 address | 2606:4700::6812:1b95 |
| comfrt.com | AAAA | IPv6 address | 2606:4700::6812:1a95 |
| comfrt.com | TXT | Text record | "MS=ms29230352" |
| comfrt.com | TXT | Text record | "NETORGFT10697041.onmicrosoft.com" |
| comfrt.com | TXT | Text record | "_4q1z2lvkpatrt0yvx311q3bnk6dsfo9" |
| comfrt.com | TXT | Text record | "google-site-verification=3BqvrOBzdNvuru9WYpgtjgs3gXkVY57XGpJ1YTNF-aY" |
| comfrt.com | TXT | Text record | "google-site-verification=PfkAJO0OHW4s85loPk4G4kCHRe2SXgRAZGxGs_RV9YU" |
| comfrt.com | TXT | Text record | "google-site-verification=XhoLqKAC9egIIYpSBmvU-Ea2uetzX4Da61fZtRmzmkw" |
| comfrt.com | TXT | Text record | "google-site-verification=iM_LwDePpG6p-EqIPWhKxZn9BPB2Y32FsYlDgZ2AEvc" |
| comfrt.com | TXT | Text record | "klaviyo-site-verification=RJji5T" |
| comfrt.com | TXT | Text record | "shopify-verification-code=AMjk4GOqw3urKxfS3pj7v5DLyNDzQe" |
| comfrt.com | SPF | Sender Policy Framework | "v=spf1 include:secureserver.net include:_spf.google.com include:mail.zendesk.com -all" |
| _dmarc.comfrt.com | TXT | Text record | "v=DMARC1; p=quarantine; pct=100; rua=mailto:dmarc@comfrt.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
| Software / Version | Category |
|---|---|
| Shopify | Ecommerce |
| Snowplow Analytics | Analytics, IaaS |
| LiveIntent | Email, Advertising |
| Pinterest Ads | Advertising |
| Cloudflare | CDN |
| Northbeam | Analytics |
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.