Vulnerability Scan Result
| Title: | US PERENNIALS |
| Description: | Shop our online perennial nursery for North American native plants and nativars. Sustainably grown, pollinator-friendly perennials shipped directly to your door. Discover the beauty of perennial gardening year-round at US Perennials. Explore a stunning array of hardy perennials, from vibrant spring blooms to fall foliage wonders. Get expert advice, find the perfect plants for your garden, and transform your outdoor space. Start your perennial journey today! Garden naturally! |
| ip_address | 192.200.160.248 |
| country | US  |
| network_name | BigCommerce Inc. |
| asn | AS399566 |
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 | https-alt | cloudflare - |
| Software / Version | Category |
|---|---|
| Trustpilot | Reviews |
| Google Cloud | IaaS |
| Google Cloud CDN | CDN |
| FancyBox 3.5.7 | JavaScript libraries |
| Google Font API | Font scripts |
| ZURB Foundation 5.5.3 | UI frameworks |
| Bootstrap 5 | UI frameworks |
| LazySizes | JavaScript libraries, Performance |
| core-js 3.49.0 | JavaScript libraries |
| Goober | JavaScript libraries |
| Google Analytics GA4 | Analytics |
| HTTP/3 | Miscellaneous |
| jQuery 3.7.1 | JavaScript libraries |
| lit-html 1.1.2 | JavaScript libraries |
| MySQL | Databases |
| PHP | Programming languages |
| DoubleClick Floodlight | Advertising |
| WordPress | CMS, Blogs |
| BigCommerce | Ecommerce |
| Cloudflare | CDN |
| Cloudflare Bot Management | Security |
| reCAPTCHA | Security |
| Google Tag Manager | Tag managers |
| HSTS | Security |
| Cart Functionality | Ecommerce |
| YouTube | Video players |
Web Application Vulnerabilities
Evidence
| URL | Cookie Name | Evidence |
|---|---|---|
| https://www.usperennials.com/ | SF-CSRF-TOKEN, fornax_anonymousId | The server responded with Set-Cookie header(s) that does not specify the HttpOnly flag: Set-Cookie: SF-CSRF-TOKEN=fd13d54d-ca67-47ca-b608-5684e890c0c2 Set-Cookie: fornax_anonymousId=92d78f92-f67a-4cb3-a054-b645ead32a91 |
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://www.usperennials.com/ | 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-1021 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Evidence |
|---|---|
| https://www.usperennials.com/ | 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 | Method | Parameters | Evidence |
|---|---|---|---|
| https://www.usperennials.com/pennisetum-alopecuroides-jambalaya-fountain-grass-jambalaya-sterile-not-seeding/ | GET | Headers: User-Agent=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0 Safari/537.36 Cookies: SF-CSRF-TOKEN=da88f101-9ec4-4586-a34c-c60f9748cf21 SHOP_SESSION_TOKEN=116b96da-112f-467b-8659-5cf6b3beef81 Shopper-Pref=31523E359B2C5DE1831344... | Suspicious comment TODO found in: |
Vulnerability description
We have discovered that the target application's code contains suspicious comments that may be related to potential bugs, incomplete functionality, or weaknesses. These comments often arise during development and testing phases but are inadvertently left in the code.
Risk description
The risk exists that attackers could analyze these comments to identify vulnerabilities or weaknesses in the application. While comments themselves do not directly lead to security breaches, they may guide attackers to focus their efforts on specific parts of the application, potentially uncovering and exploiting vulnerabilities.
Recommendation
Remove comments that suggest the presence of bugs, incomplete functionality, or weaknesses, before deploying the application.
Classification
| CWE | CWE-546 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| Software / Version | Category |
|---|---|
| Trustpilot | Reviews |
| Google Cloud | IaaS |
| Google Cloud CDN | CDN |
| FancyBox 3.5.7 | JavaScript libraries |
| Google Font API | Font scripts |
| ZURB Foundation 5.5.3 | UI frameworks |
| Bootstrap 5 | UI frameworks |
| LazySizes | JavaScript libraries, Performance |
| core-js 3.49.0 | JavaScript libraries |
| Goober | JavaScript libraries |
| Google Analytics GA4 | Analytics |
| HTTP/3 | Miscellaneous |
| jQuery 3.7.1 | JavaScript libraries |
| lit-html 1.1.2 | JavaScript libraries |
| MySQL | Databases |
| PHP | Programming languages |
| DoubleClick Floodlight | Advertising |
| WordPress | CMS, Blogs |
| BigCommerce | Ecommerce |
| Cloudflare | CDN |
| Cloudflare Bot Management | Security |
| reCAPTCHA | Security |
| Google Tag Manager | Tag managers |
| HSTS | Security |
| Cart Functionality | Ecommerce |
| YouTube | Video players |
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
| CWE | CWE-200 |
| 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).
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.
Classification
| CWE | CWE-1188 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Method | Parameters | Evidence |
|---|---|---|---|
| https://www.usperennials.com/ | GET | Headers: User-Agent=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0 Safari/537.36 | Email Address: info@usperennials.com |
Vulnerability description
We noticed that this web application exposes email addresses, which might be unintended. While not inherently a vulnerability, this information could be leveraged in social engineering or spam related activities.
Risk description
The risk is that exposed email addresses within the application could be accessed by unauthorized parties. This could lead to privacy violations, spam, phishing attacks, or other forms of misuse.
Recommendation
Compartmentalize the application to have 'safe' areas where trust boundaries can be unambiguously drawn. Do not allow email addresses to go outside of the trust boundary, and always be careful when interfacing with a compartment outside of the safe area.
Classification
| CWE | CWE-200 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Infrastructure Vulnerabilities
Evidence
We found insecure DNS cookie usage on the following nameservers: ns2.bigcommerce.com, ns1.bigcommerce.com, ns3.bigcommerce.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 Bot Management | Security |
| 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 Bot Management | Security |
| 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 Bot Management | Security |
| 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 Bot Management | Security |
| 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 Bot Management | Security |
| 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 |
|---|---|---|---|
| www.usperennials.com | A | IPv4 address | 192.200.160.248 |
| www.usperennials.com | NS | Name server | ns2.bigcommerce.com |
| www.usperennials.com | NS | Name server | ns1.bigcommerce.com |
| www.usperennials.com | NS | Name server | ns3.bigcommerce.com |
| www.usperennials.com | MX | Mail server | 0 usperennials-com.mail.protection.outlook.com |
| www.usperennials.com | SOA | Start of Authority | ns1.bigcommerce.com. serverops.bigcommerce.com. 2024021701 10800 3600 604800 10800 |
| www.usperennials.com | SPF | Sender Policy Framework | "v=spf1 include:_spf.bigcommerce.com include:spf.protection.outlook.com -all" |
| www.usperennials.com | CNAME | Canonical name | usperennials.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
| Operating System | Accuracy |
|---|---|
| FreeBSD 11.0-RELEASE | 91% |
Vulnerability description
OS Detection
Evidence
| Software / Version | Category |
|---|---|
| Cloudflare Bot Management | Security |
| 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 |
|---|---|
| Cart Functionality | Ecommerce |
| BigCommerce | Ecommerce |
| WordPress | CMS, Blogs |
| MySQL | Databases |
| PHP | Programming languages |
| YouTube | Video players |
| Bootstrap 5 | UI frameworks |
| ZURB Foundation 5.5.3 | UI frameworks |
| Google Cloud | IaaS |
| lit-html 1.1.2 | JavaScript libraries |
| Goober | JavaScript libraries |
| Cloudflare Bot Management | Security |
| Trustpilot | Reviews |
| LazySizes | JavaScript libraries, Performance |
| jQuery 3.7.1 | JavaScript libraries |
| Google Tag Manager | Tag managers |
| Google Analytics GA4 | Analytics |
| FancyBox 3.5.7 | JavaScript libraries |
| core-js 3.49.0 | JavaScript libraries |
| reCAPTCHA | Security |
| Google Font API | Font scripts |
| DoubleClick Floodlight | Advertising |
| HSTS | Security |
| Google Cloud CDN | CDN |
| 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.