Vulnerability Scan Result
| Title: | Grab 'N Go Kits |
| Description: | No description found |
| ip_address | 35.190.19.52 |
| country | US  |
| network_name | Google LLC |
| asn | AS396982 |
80/tcp | http | openresty - |
443/tcp | https | OpenResty web app server - |
| Software / Version | Category |
|---|---|
| Google Hosted Libraries | CDN |
| Google Font API | Font scripts |
| ZURB Foundation 5.5.3 | UI frameworks |
| LazySizes | JavaScript libraries, Performance |
| core-js 3.49.0 | JavaScript libraries |
| Nginx | Web servers, Reverse proxies |
| OpenResty | Web servers |
| PHP | Programming languages |
| Webpack | Miscellaneous |
| BigCommerce | Ecommerce |
| HSTS | Security |
| UPS | Shipping carriers |
| Cart Functionality | Ecommerce |
Web Application Vulnerabilities
Evidence
| URL | Cookie Name | Evidence |
|---|---|---|
| https://grabngokits.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=fc9e2027-d6c3-4b58-8def-38fa03fd4464 Set-Cookie: fornax_anonymousId=b1e5661c-024f-4f76-853f-335a6e033aaa |
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://grabngokits.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
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 | Method | Parameters | Evidence |
|---|---|---|---|
| https://grabngokits.com/frosty-mittens/ | 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=cec879f5-7a2a-4b05-80c7-509ac64dac2d SHOP_SESSION_TOKEN=c5a36321-9da1-4b50-87ae-e25b158453d6 Shopper-Pref=FBC311B08A5EAE58062BCD... | 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 |
|---|---|
| Google Hosted Libraries | CDN |
| Google Font API | Font scripts |
| ZURB Foundation 5.5.3 | UI frameworks |
| LazySizes | JavaScript libraries, Performance |
| core-js 3.49.0 | JavaScript libraries |
| Nginx | Web servers, Reverse proxies |
| OpenResty | Web servers |
| PHP | Programming languages |
| Webpack | Miscellaneous |
| BigCommerce | Ecommerce |
| HSTS | Security |
| UPS | Shipping carriers |
| 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.
Classification
| CWE | CWE-200 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Evidence |
|---|---|
| https://grabngokits.com/ | 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-1021 |
| 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.
Classification
| CWE | CWE-1188 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
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.grabngokits.com | TXT | Text record | "v=DMARC1; p=reject; rua=mailto:dmarc@avesi.com; ruf=mailto:dmarc@avesi.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
| Operating System | Accuracy |
|---|---|
| Crestron XPanel control system | 90% |
Vulnerability description
OS Detection
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| grabngokits.com | A | IPv4 address | 35.190.19.52 |
| grabngokits.com | NS | Name server | ns2.avenirsolutions.com |
| grabngokits.com | NS | Name server | ns1.avenirsolutions.com |
| grabngokits.com | MX | Mail server | 10 mail.avesi.com |
| grabngokits.com | SOA | Start of Authority | ns1.avenirsolutions.com. webhosting.avenirsolutions.com. 2021112301 3600 1800 604800 3600 |
| grabngokits.com | SPF | Sender Policy Framework | "v=spf1 ip4:69.147.162.0/24 ip4:38.97.126.0/24 ip4:208.85.0.64/28 -all" |
| _dmarc.grabngokits.com | TXT | Text record | "v=DMARC1; p=reject; rua=mailto:dmarc@avesi.com; ruf=mailto:dmarc@avesi.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
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| grabngokits.com | SPF | Sender Policy Framework | "v=spf1 ip4:69.147.162.0/24 ip4:38.97.126.0/24 ip4:208.85.0.64/28 -all" |
Evidence
| Software / Version | Category |
|---|---|
| Cart Functionality | Ecommerce |
| BigCommerce | Ecommerce |
| PHP | Programming languages |
| ZURB Foundation 5.5.3 | UI frameworks |
| Nginx | Web servers, Reverse proxies |
| UPS | Shipping carriers |
| OpenResty | Web servers |
| Google Hosted Libraries | CDN |
| LazySizes | JavaScript libraries, Performance |
| core-js 3.49.0 | JavaScript libraries |
| Google Font API | Font scripts |
| HSTS | Security |
| Webpack | 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.