Vulnerability Scan Result
| Title: | Meady's | Premium Raw & Freeze-Dried Pet Food for Dogs & Cats |
| Description: | Discover Meadys, your trusted source for premium raw and freeze-dried pet food for dogs and cats. Locally made with human-grade, grain-free ingredients, our meals are designed to promote health, longevity, and happiness. Convenient home delivery available. Try Meadys today! |
| ip_address | 23.227.38.68 |
| 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 |
|---|---|
| cdnjs | CDN |
| Facebook Pixel 2.9.256 | Analytics |
| LazySizes | JavaScript libraries, Performance |
| core-js 2.6.12 | JavaScript libraries |
| Google Analytics GA4 | Analytics |
| Growave | Marketing automation, Authentication |
| HTTP/3 | Miscellaneous |
| Zotabox | Marketing automation |
| jQuery 3.5.1 | JavaScript libraries |
| MailChimp | Marketing automation, Email |
| Open Graph | Miscellaneous |
| PayPal | Payment processors |
| PhotoSwipe | Photo galleries, JavaScript libraries |
| Shop Pay | Payment processors |
| Shopify | Ecommerce |
| American Express | Payment processors |
| Apple Pay | Payment processors |
| Cloudflare | CDN |
| Google Tag Manager | Tag managers |
| hCaptcha 1 | Security |
| Klaviyo | Marketing automation |
| Klaviyo Reviews | Reviews |
| Mastercard | Payment processors |
| HSTS | Security |
| Visa | Payment processors |
| Cart Functionality | Ecommerce |
| Yotpo Reviews | Reviews |
Web Application Vulnerabilities
Evidence
| URL | Cookie Name | Evidence |
|---|---|---|
| https://meadys.com/ | 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=CA Set-Cookie: cart_currency=CAD Set-Cookie: _shopify_y=0aa18f00-6a14-4c9d-90b1-2002bbc02126 Set-Cookie: _shopify_s=4b51cc87-bfe1-4515-ae38-8f0b43e1a113 |
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://meadys.com/ | _shopify_y, _shopify_s | Set-Cookie: _shopify_y=0aa18f00-6a14-4c9d-90b1-2002bbc02126 Set-Cookie: _shopify_s=4b51cc87-bfe1-4515-ae38-8f0b43e1a113 |
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 | Method | Parameters | Evidence |
|---|---|---|---|
| https://meadys.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 | 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-209 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Evidence |
|---|---|
| https://meadys.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-693 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Evidence |
|---|---|
| https://meadys.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
| Software / Version | Category |
|---|---|
| cdnjs | CDN |
| Facebook Pixel 2.9.256 | Analytics |
| LazySizes | JavaScript libraries, Performance |
| core-js 2.6.12 | JavaScript libraries |
| Google Analytics GA4 | Analytics |
| Growave | Marketing automation, Authentication |
| HTTP/3 | Miscellaneous |
| Zotabox | Marketing automation |
| jQuery 3.5.1 | JavaScript libraries |
| MailChimp | Marketing automation, Email |
| Open Graph | Miscellaneous |
| PayPal | Payment processors |
| PhotoSwipe | Photo galleries, JavaScript libraries |
| Shop Pay | Payment processors |
| Shopify | Ecommerce |
| American Express | Payment processors |
| Apple Pay | Payment processors |
| Cloudflare | CDN |
| Google Tag Manager | Tag managers |
| hCaptcha 1 | Security |
| Klaviyo | Marketing automation |
| Klaviyo Reviews | Reviews |
| Mastercard | Payment processors |
| HSTS | Security |
| Visa | Payment processors |
| Cart Functionality | Ecommerce |
| Yotpo Reviews | Reviews |
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 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
| URL | Method | Parameters | Evidence |
|---|---|---|---|
| https://meadys.com/policies/terms-of-service | 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: _shopify_analytics=:AZwgt3vnAAEAXy-Q1roEdjdH_l1tTE2RSbyaL-SxBqiUDu4Zp6uux9TurNiP0yDVDsmF: _shopify_essential=:AZwgt3vZAAEACg7AnYv53STeFF0XGoPN... | Email Address: alex.tsyrfa@gmail.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
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| _dmarc.meadys.com | TXT | Text record | "v=DMARC1; p=none" |
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.meadys.com | TXT | Text record | "v=DMARC1; p=none" |
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.meadys.com | TXT | Text record | "v=DMARC1; p=none" |
Vulnerability description
We found that the DMARC record for the domain is not configured with rua tag. When a DMARC record is not configured with the rua (Reporting URI for Aggregate Reports) tag, the domain owner misses out on critical feedback regarding the domain's email authentication performance. Aggregate reports are essential for monitoring how a domain's DMARC policy is applied across various mail servers and whether legitimate or malicious emails are being sent on behalf of the domain. Without this reporting, domain administrators have no visibility into how their DMARC policy is being enforced, which hinders their ability to detect potential spoofing or authentication issues.
Risk description
The absence of rua reporting creates a significant blind spot in the domain's email security posture. Without aggregate reports, domain administrators cannot track DMARC compliance across email sent from their domain, leaving them unaware of potential misconfigurations or unauthorized use of their domain for malicious purposes, such as phishing or spoofing. This lack of visibility increases the risk of undetected spoofing attempts, which could damage the domain's reputation and lead to financial, operational, or reputational harm. Moreover, legitimate email issues, such as misaligned SPF or DKIM configurations, may also go unnoticed, affecting email deliverability.
Recommendation
We recommend configuring the rua tag in the DMARC record to receive aggregate reports from mail servers. This tag should point to a reliable email address or monitoring service capable of handling DMARC aggregate reports, such as rua=mailto:dmarc-reports@example.com. These reports provide valuable insights into how email from the domain is being treated by receiving mail servers, highlighting potential authentication issues and attempts to spoof the domain. Regularly reviewing these reports will help ensure the DMARC policy is properly enforced and that any email authentication failures are addressed in a timely manner.
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| _dmarc.meadys.com | TXT | Text record | "v=DMARC1; p=none" |
Vulnerability description
We found that the target uses p=none in the DMARC policy. The DMARC policy set to p=none means that the domain owner is not taking any action on emails that fail DMARC validation. This configuration effectively disables enforcement, allowing potentially spoofed or fraudulent emails to be delivered without any additional scrutiny.
Risk description
Emails that fail DMARC checks are still delivered to recipients. This leaves the domain highly vulnerable to email spoofing and phishing attacks, as malicious actors can impersonate the domain without facing any consequences from DMARC enforcement.
Recommendation
We recommend changing the DMARC policy to p=quarantine or, ideally, p=reject to actively block or quarantine emails that fail DMARC validation. This will enhance the security of your domain against spoofing and phishing attacks by ensuring that only legitimate emails are delivered.
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| meadys.com | A | IPv4 address | 23.227.38.68 |
| meadys.com | NS | Name server | ns-cloud-b4.googledomains.com |
| meadys.com | NS | Name server | ns-cloud-b1.googledomains.com |
| meadys.com | NS | Name server | ns-cloud-b3.googledomains.com |
| meadys.com | NS | Name server | ns-cloud-b2.googledomains.com |
| meadys.com | MX | Mail server | 1 mx.meadys.com.cust.b.hostedemail.com |
| meadys.com | SOA | Start of Authority | ns-cloud-b1.googledomains.com. cloud-dns-hostmaster.google.com. 1 21600 3600 259200 300 |
| meadys.com | AAAA | IPv6 address | 2620:127:f00f:8:: |
| _dmarc.meadys.com | TXT | Text record | "v=DMARC1; p=none" |
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
| Software / Version | Category |
|---|---|
| Shopify | Ecommerce |
| PayPal | Payment processors |
| Shop Pay | Payment processors |
| HSTS | Security |
| Cloudflare | CDN |
| HTTP/3 | Miscellaneous |
| Yotpo Reviews | Reviews |
| MailChimp | Marketing automation, Email |
| Klaviyo | Marketing automation |
| hCaptcha 1 | Security |
| Google Tag Manager | Tag managers |
| Google Analytics GA4 | Analytics |
| Facebook Pixel 2.9.256 | Analytics |
| cdnjs | CDN |
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
| Operating System | Accuracy |
|---|---|
| FreeBSD 12.0-RELEASE | 92% |
Vulnerability description
OS Detection
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.