Vulnerability Scan Result
| Title: | Eco-Friendly iPhone, Google and Samsung Cases - 100% Compostable – Pela Case |
| Description: | World's First 100% Compostable, Eco-Friendly iPhone and Android phone cases working towards plastic free oceans! |
| ip_address | 23.227.38.65 |
| country | CA  |
| network_name | Cloudflare Inc |
| asn | AS13335 |
80/tcp | http | Cloudflare http proxy - |
443/tcp | https | Cloudflare http proxy - |
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 | https | Cloudflare http proxy - |
| Software / Version | Category |
|---|---|
| Amazon Web Services | PaaS |
| Amazon S3 | CDN |
| Blotout EdgeTag | Marketing automation |
| Fast Bundle | Shopify apps |
| core-js 3.37.0 | JavaScript libraries |
| HTTP/3 | Miscellaneous |
| PayPal | Payment processors |
| Rebuy | Personalisation, Shopify apps |
| Recharge | Payment processors |
| Rise.ai | Loyalty & rewards, Referral marketing |
| Searchspring | Search engines |
| Shopify | Ecommerce |
| Cloudflare | CDN |
| Google Tag Manager | Tag managers |
| Klaviyo | Marketing automation |
| Northbeam | Analytics |
| Postscript | Marketing automation |
| HSTS | Security |
| Richpanel | CRM |
| Cart Functionality | Ecommerce |
Web Application Vulnerabilities
Evidence
| URL | Cookie Name | Evidence |
|---|---|---|
| https://pelacase.ca/ | localization, cart_currency | The server responded with Set-Cookie header(s) that does not specify the HttpOnly flag: Set-Cookie: localization=CA Set-Cookie: cart_currency=CAD |
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 | Evidence |
|---|---|
| https://pelacase.ca/ | 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
| Software / Version | Category |
|---|---|
| Amazon Web Services | PaaS |
| Amazon S3 | CDN |
| Blotout EdgeTag | Marketing automation |
| Fast Bundle | Shopify apps |
| core-js 3.37.0 | JavaScript libraries |
| HTTP/3 | Miscellaneous |
| PayPal | Payment processors |
| Rebuy | Personalisation, Shopify apps |
| Recharge | Payment processors |
| Rise.ai | Loyalty & rewards, Referral marketing |
| Searchspring | Search engines |
| Shopify | Ecommerce |
| Cloudflare | CDN |
| Google Tag Manager | Tag managers |
| Klaviyo | Marketing automation |
| Northbeam | Analytics |
| Postscript | Marketing automation |
| HSTS | Security |
| Richpanel | CRM |
| Cart Functionality | Ecommerce |
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
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://pelacase.ca/ | 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 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.
Evidence
Vulnerability description
Website is accessible.
Infrastructure Vulnerabilities
Evidence
We checked 2056 selectors but found no DKIM records.
Vulnerability description
We found that no DKIM record was configured. When a DKIM (DomainKeys Identified Mail) record is not present for a domain, it means that outgoing emails from that domain are not cryptographically signed. DKIM is a critical component of email authentication, allowing recipients to verify that an email was genuinely sent from an authorized server and that the message has not been altered in transit. The absence of a DKIM record leaves the domain vulnerable to email spoofing and phishing attacks, as attackers can send fraudulent emails that appear to originate from the domain without any cryptographic verification.
Risk description
Without a DKIM record, recipients have no way of verifying the integrity or authenticity of emails sent from the domain. This increases the likelihood of phishing and spoofing attacks, where malicious actors impersonate the domain to send fraudulent emails. This can lead to significant security incidents, such as credential theft, financial fraud, or the distribution of malware. Additionally, many email providers use DKIM as part of their spam and reputation filters, meaning that emails from a domain without DKIM may be flagged as spam or rejected, impacting the deliverability and reputation of legitimate emails.
Recommendation
We recommend implementing DKIM for your domain to enhance email security and protect your brand from email-based attacks. Generate a DKIM key pair (public and private keys), publish the public key in the DNS under the appropriate selector, and configure your email servers to sign outgoing messages using the private key. Ensure that the DKIM key length is at least 1024 bits to prevent cryptographic attacks. Regularly monitor DKIM signatures to ensure the system is functioning correctly and update keys periodically to maintain security.
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| _dmarc.pelacase.ca | TXT | Text record | "v=DMARC1;p=none;sp=none;pct=100;rua=mailto:772d4ee1d3@rua.easydmarc.us,mailto:security@pelacase.com;ruf=mailto:772d4ee1d3@ruf.easydmarc.us,mailto:security@pelacase.com;ri=86400;aspf=r;adkim=r;fo=1" |
Vulnerability description
We found that the DMARC record for the domain is configured with sp=none, meaning that no policy is enforced for subdomains. This allows subdomains to send emails without being subject to DMARC checks, making it easier for attackers to spoof emails from these subdomains. Subdomains are often overlooked in email security, and attackers can exploit this misconfiguration to launch phishing or spoofing attacks from seemingly legitimate subdomains of a protected domain.
Risk description
When the DMARC record is configured with sp=none, subdomains are not subject to DMARC enforcement, allowing attackers to spoof emails from subdomains without being blocked. This creates a significant risk of phishing and impersonation attacks, where malicious emails appear to originate from trusted subdomains. These spoofed emails can be used to deceive users or damage the organization's reputation, undermining the security benefits of DMARC for the primary domain.
Recommendation
To mitigate the risk, we recommend that the subdomain policy should be updated to sp=reject to ensure that any email failing DMARC checks from subdomains is automatically rejected. This will help prevent unauthorized emails from being sent from subdomains, reducing the risk of spoofing and phishing. Additionally, it's important to regularly monitor DMARC reports to track email activity from subdomains and adjust policies as needed to maintain consistent security across the entire domain.
Evidence
We found insecure DNS cookie usage on the following nameservers: ns35.domaincontrol.com, ns36.domaincontrol.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
| Software / Version | Category |
|---|---|
| Cloudflare | CDN |
| HTTP/3 | 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.
Evidence
| Software / Version | Category |
|---|---|
| Cloudflare | CDN |
| HTTP/3 | 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.
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| pelacase.ca | A | IPv4 address | 23.227.38.65 |
| pelacase.ca | NS | Name server | ns35.domaincontrol.com |
| pelacase.ca | NS | Name server | ns36.domaincontrol.com |
| pelacase.ca | MX | Mail server | 10 aspmx.l.google.com |
| pelacase.ca | MX | Mail server | 20 alt1.aspmx.l.google.com |
| pelacase.ca | MX | Mail server | 30 alt2.aspmx.l.google.com |
| pelacase.ca | MX | Mail server | 40 alt3.aspmx.l.google.com |
| pelacase.ca | MX | Mail server | 50 alt4.aspmx.l.google.com |
| pelacase.ca | SOA | Start of Authority | ns35.domaincontrol.com. dns.jomax.net. 2024012900 28800 7200 604800 600 |
| pelacase.ca | TXT | Text record | "klaviyo-site-verification=YwdpTB" |
| pelacase.ca | TXT | Text record | "google-site-verification=Ob2IiURXAJfC42D69U38PFsjTQhKxItAR2WdHM38hmY" |
| pelacase.ca | TXT | Text record | "google-site-verification=Lez6ovF01Dr4y52BdL2nx73m0ScgjRsFkWqhbulNr8w" |
| pelacase.ca | TXT | Text record | "facebook-domain-verification=w6za34sglcag2xyirqeslf9g92m1gv" |
| pelacase.ca | TXT | Text record | "google-site-verification=oGpARMNMRTZ2wZR5aGrzSFxZXzGb0yoFcOhH1WmiFxE" |
| pelacase.ca | SPF | Sender Policy Framework | "v=spf1 include:mail.zendesk.com ?all" |
| _dmarc.pelacase.ca | TXT | Text record | "v=DMARC1;p=none;sp=none;pct=100;rua=mailto:772d4ee1d3@rua.easydmarc.us,mailto:security@pelacase.com;ruf=mailto:772d4ee1d3@ruf.easydmarc.us,mailto:security@pelacase.com;ri=86400;aspf=r;adkim=r;fo=1" |
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 |
|---|---|
| Cloudflare | CDN |
| HTTP/3 | 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.
Evidence
| Operating System | Accuracy |
|---|---|
| FreeBSD 12.0-RELEASE | 92% |
Vulnerability description
OS Detection
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| pelacase.ca | SPF | Sender Policy Framework | "v=spf1 include:mail.zendesk.com ?all" |
Evidence
| Software / Version | Category |
|---|---|
| Cloudflare | CDN |
| HTTP/3 | 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.
Evidence
| Software / Version | Category |
|---|---|
| Cloudflare | CDN |
| HTTP/3 | 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.
Evidence
| Software / Version | Category |
|---|---|
| Cloudflare | CDN |
| HTTP/3 | 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.
Evidence
| Software / Version | Category |
|---|---|
| Shopify | Ecommerce |
| Searchspring | Search engines |
| PayPal | Payment processors |
| Venmo | Payment processors |
| Apple Pay | Payment processors |
| HSTS | Security |
| Cloudflare | CDN |
| HTTP/3 | Miscellaneous |
| Klaviyo | Marketing automation |
| Google Tag Manager | Tag managers |
| Priority Hints | Performance |
| Google Font API | Font scripts |
| Open Graph | Miscellaneous |
| core-js 3.37.0 | JavaScript libraries |
| Blotout EdgeTag | Marketing automation |
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.