Vulnerability Scan Result
| Title: | Pettadore | Intelligent Petcare |
| Description: | Healthy cats in a simple way. |
| 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 |
|---|---|
| Facebook Pixel 2.9.239 | Analytics |
| core-js 3.37.0 | JavaScript libraries |
| Google Analytics GA4 | Analytics |
| HTTP/3 | Miscellaneous |
| jQuery | JavaScript libraries |
| Open Graph | Miscellaneous |
| PayPal | Payment processors |
| Shopify | Ecommerce |
| Priority Hints | Performance |
| ActiveCampaign | Marketing automation, Email |
| Cloudflare | CDN |
| Hotjar | Analytics |
| HSTS | Security |
| Visa | Payment processors |
| Cart Functionality | Ecommerce |
Web Application Vulnerabilities
Evidence
| URL | Cookie Name | Evidence |
|---|---|---|
| https://pettadore.com/ | localization, cart_currency, _shopify_y, _shopify_s | Set-Cookie: localization=AT Set-Cookie: cart_currency=EUR Set-Cookie: _shopify_y=0715a910-e811-44e6-adc1-14482418d01c Set-Cookie: _shopify_s=43725836-8dfd-4cd6-ae9b-319afce7b0ba |
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://pettadore.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=AT Set-Cookie: cart_currency=EUR Set-Cookie: _shopify_y=0715a910-e811-44e6-adc1-14482418d01c Set-Cookie: _shopify_s=43725836-8dfd-4cd6-ae9b-319afce7b0ba |
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
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 |
|---|---|
| Facebook Pixel 2.9.239 | Analytics |
| core-js 3.37.0 | JavaScript libraries |
| Google Analytics GA4 | Analytics |
| HTTP/3 | Miscellaneous |
| jQuery | JavaScript libraries |
| Open Graph | Miscellaneous |
| PayPal | Payment processors |
| Shopify | Ecommerce |
| Priority Hints | Performance |
| ActiveCampaign | Marketing automation, Email |
| Cloudflare | CDN |
| Hotjar | Analytics |
| HSTS | Security |
| Visa | Payment processors |
| 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
| URL | Evidence |
|---|---|
| https://pettadore.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 | Evidence |
|---|---|
| https://pettadore.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 |
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
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| _dmarc.pettadore.com | TXT | Text record | "v=DMARC1; p=none; sp=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 |
|---|---|---|---|
| pettadore.com | SPF | Sender Policy Framework | "v=spf1 include:emsd1.com ~all" |
Vulnerability description
We found that the Sender Policy Framework (SPF) record for the domain is configured with ~all (soft fail), which indicates that emails from unauthorized IP addresses are not explicitly denied. Instead, the recipient mail server is instructed to treat these messages with suspicion but may still accept them. This configuration may not provide enough protection against email spoofing and unauthorized email delivery, leaving the domain more vulnerable to impersonation attempts.
Risk description
The ~all directive in an SPF record allows unauthorized emails to pass through some email servers, even though they fail SPF verification. While such emails may be marked as suspicious or placed into a spam folder, not all mail servers handle soft fail conditions consistently. This creates a risk that malicious actors can spoof the domain to send phishing emails or other fraudulent communications, potentially causing damage to the organization's reputation and leading to successful social engineering attacks.
Recommendation
We recommend changing the SPF record's ~all (soft fail) directive to -all (hard fail). The -all setting tells recipient mail servers to reject emails from any IP addresses not listed in the SPF record, providing stronger protection against email spoofing. Ensure that all legitimate IP addresses and services that send emails on behalf of your domain are properly included in the SPF record before implementing this change.
Evidence
We found insecure DNS cookie usage on the following nameservers: ns.zxcs.be, ns.zxcs.eu, ns.zxcs.nl
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.pettadore.com | TXT | Text record | "v=DMARC1; p=none; sp=none;" |
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
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| pettadore.com | SPF | Sender Policy Framework | "v=spf1 include:_spf.google.com ~all" |
Vulnerability description
We found that the Sender Policy Framework (SPF) record for the domain is configured with ~all (soft fail), which indicates that emails from unauthorized IP addresses are not explicitly denied. Instead, the recipient mail server is instructed to treat these messages with suspicion but may still accept them. This configuration may not provide enough protection against email spoofing and unauthorized email delivery, leaving the domain more vulnerable to impersonation attempts.
Risk description
The ~all directive in an SPF record allows unauthorized emails to pass through some email servers, even though they fail SPF verification. While such emails may be marked as suspicious or placed into a spam folder, not all mail servers handle soft fail conditions consistently. This creates a risk that malicious actors can spoof the domain to send phishing emails or other fraudulent communications, potentially causing damage to the organization's reputation and leading to successful social engineering attacks.
Recommendation
We recommend changing the SPF record's ~all (soft fail) directive to -all (hard fail). The -all setting tells recipient mail servers to reject emails from any IP addresses not listed in the SPF record, providing stronger protection against email spoofing. Ensure that all legitimate IP addresses and services that send emails on behalf of your domain are properly included in the SPF record before implementing this change.
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| pettadore.com | SPF | Sender Policy Framework | "v=spf1 include:_spf.google.com ~all" |
| pettadore.com | SPF | Sender Policy Framework | "v=spf1 include:emsd1.com ~all" |
Vulnerability description
We found that the target has more than one configured DNS SPF (Sender Policy Framework) record. SPF is designed to prevent email spoofing by specifying which mail servers are allowed to send email on behalf of a domain. According to RFC 7208, a domain must have only one SPF record. Multiple SPF records can cause validation issues, leading to failed email authentication checks. This could impact email deliverability, and legitimate emails may be rejected or marked as spam.
Risk description
Having multiple SPF records poses a significant risk to email security and deliverability. When a receiving email server encounters more than one SPF record, it might fail to properly validate the SPF configuration, leading to the rejection of legitimate emails or their classification as spam. This can negatively affect business operations by disrupting email communication with customers, partners, or internal stakeholders. Furthermore, failure to comply with SPF best practices can make the domain more vulnerable to email spoofing attacks, which could damage the organization's reputation and lead to phishing attempts using the domain name.
Recommendation
We recommend removing any redundant or conflicting SPF records and ensuring that only one SPF record is present. The multiple records should be merged into a single SPF entry that includes all necessary authorized mail servers. For example, if two SPF records exist, they can be combined into one as follows:\nv=spf1 include:spf1.example.com include:spf2.example.com -all\nAfterward, verify that the single SPF record covers all the intended mail servers. Test the SPF configuration using email testing tools to confirm that it works correctly and that email deliverability is not negatively impacted.
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| _dmarc.pettadore.com | TXT | Text record | "v=DMARC1; p=none; sp=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
| DKIM selector | Key type | Key size | Value |
|---|---|---|---|
| x | rsa | 786 | "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA4E9InIN7V7hGuVywNvL1Av4UdndBaAVu6lpy+AxUrw/nKvl6f0fHUlgBV4AUyo1gBogyvT3LIkute0KOJ1vWlao" "TVsUbnT2MKFYABxsJbZVtTM8CCf7N+6zHPa8Hsrm7+BAQrX0u5Z57ywnZBNoOFRMyge24AU55O93M/I5oHmSAesQfpHZ8B7Gfo32evdONdOX5y+xyy8U83Rr+3o7Ux6RoXLkV6qgoqdHaSmGxNei1m" "tmDLrm9Ctl4QrF1xbDiJvdVhreJNAcCSJ2Hr1koBcGTVDdv7M9B3tWzBFY8ZZLyBR8jkcnYeDWe23rpTqkHYDjKyC17cwG9Ifi1OH3e5wIDAQAB" |
Vulnerability description
We found that the DKIM key length is under 1024-bit. When a DKIM (DomainKeys Identified Mail) key length is under 1024-bit, it is considered weak by modern cryptographic standards. Shorter key lengths, such as 512 or 768 bits, are vulnerable to brute-force attacks, where an attacker could potentially forge a valid DKIM signature for a domain. This undermines the entire purpose of DKIM, which is to authenticate email messages and prevent email spoofing by verifying that the message headers have not been tampered with. A DKIM key under 1024 bits significantly reduces the difficulty for attackers to break the signature.
Risk description
The primary risk of using a DKIM key with fewer than 1024 bits is that it weakens the domain's email authentication security, making it more susceptible to brute-force attacks. If an attacker successfully forges a DKIM signature, they can impersonate legitimate senders and send fraudulent or phishing emails that appear authentic to the recipient. This can lead to financial losses, reputational damage, and an increased risk of targeted attacks, as recipients are more likely to trust emails that pass DKIM verification.
Recommendation
We recommend using a DKIM key with a length of at least 1024 bits. Ideally, 2048-bit keys should be used, as they provide a higher level of security and are more resistant to brute-force attacks. Organizations should regularly audit their DKIM configurations and rotate cryptographic keys periodically to maintain security. In addition, any DKIM keys that are less than 1024 bits should be immediately replaced with stronger keys to prevent exploitation.
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| _dmarc.pettadore.com | TXT | Text record | "v=DMARC1; p=none; sp=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
| 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 |
|---|---|---|---|
| pettadore.com | A | IPv4 address | 23.227.38.65 |
| pettadore.com | NS | Name server | ns.zxcs.be |
| pettadore.com | NS | Name server | ns.zxcs.eu |
| pettadore.com | NS | Name server | ns.zxcs.nl |
| pettadore.com | MX | Mail server | 5 ALT2.ASPMX.L.GOOGLE.com |
| pettadore.com | MX | Mail server | 10 ALT3.ASPMX.L.GOOGLE.com |
| pettadore.com | MX | Mail server | 5 ALT1.ASPMX.L.GOOGLE.com |
| pettadore.com | MX | Mail server | 1 ASPMX.L.GOOGLE.com |
| pettadore.com | MX | Mail server | 10 ALT4.ASPMX.L.GOOGLE.com |
| pettadore.com | SOA | Start of Authority | ns.zxcs.nl. hostmaster.pettadore.com. 2021122811 600 3600 1209600 86400 |
| pettadore.com | TXT | Text record | "google-site-verification=SVQLt95v7-oqlERg9QoB4HWykJmZ9vSQdyFRGY5I0GI" |
| pettadore.com | TXT | Text record | "google-site-verification=QLYJrIZbIygtViRebZT6UpeCgSeyPbRcAtoKI8TouuM" |
| pettadore.com | TXT | Text record | "facebook-domain-verification=jh1osr0hmdxb5gcntl05754e8npe5e" |
| pettadore.com | SPF | Sender Policy Framework | "v=spf1 include:_spf.google.com ~all" |
| pettadore.com | SPF | Sender Policy Framework | "v=spf1 include:emsd1.com ~all" |
| _dmarc.pettadore.com | TXT | Text record | "v=DMARC1; p=none; sp=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
| Operating System | Accuracy |
|---|---|
| FreeBSD 12.0-RELEASE | 92% |
Vulnerability description
OS Detection
Evidence
| DKIM selector | Key type | Key size | Value |
|---|---|---|---|
| x | rsa | 786 | "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA4E9InIN7V7hGuVywNvL1Av4UdndBaAVu6lpy+AxUrw/nKvl6f0fHUlgBV4AUyo1gBogyvT3LIkute0KOJ1vWlao" "TVsUbnT2MKFYABxsJbZVtTM8CCf7N+6zHPa8Hsrm7+BAQrX0u5Z57ywnZBNoOFRMyge24AU55O93M/I5oHmSAesQfpHZ8B7Gfo32evdONdOX5y+xyy8U83Rr+3o7Ux6RoXLkV6qgoqdHaSmGxNei1m" "tmDLrm9Ctl4QrF1xbDiJvdVhreJNAcCSJ2Hr1koBcGTVDdv7M9B3tWzBFY8ZZLyBR8jkcnYeDWe23rpTqkHYDjKyC17cwG9Ifi1OH3e5wIDAQAB" |
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 |
|---|---|
| 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 |
| jQuery | JavaScript libraries |
| Hotjar | Analytics |
| Google Analytics GA4 | Analytics |
| Facebook Pixel 2.9.239 | Analytics |
| ActiveCampaign | Marketing automation, Email |
| HSTS | 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.