Vulnerability Scan Result
| Title: | Utmify - Trackeie suas vendas de forma precisa! |
| Description: | Trackeie suas vendas de forma precisa e escale 40% a mais, sem gastar mais dinheiro. Comece a escalar da forma correta em menos de 5 minutos! |
| ip_address | 172.67.68.221 |
| country | - |
| network_name | Cloudflare, Inc. |
| asn | AS13335 |
| ip_address | 104.26.11.205 |
| country | - |
| network_name | Cloudflare, Inc. |
| asn | AS13335 |
| ip_address | 104.26.10.205 |
| country | - |
| network_name | Cloudflare, Inc. |
| asn | AS13335 |
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 | http | cloudflare - |
| Software / Version | Category |
|---|---|
| Google Ads | Advertising |
| TikTok Pixel | Analytics |
| Facebook Login | Authentication |
| Facebook Pixel 2.9.300 | Analytics |
| Fly.io | PaaS |
| Bootstrap | UI frameworks |
| core-js 3.32.2 | JavaScript libraries |
| Google Analytics GA4 | Analytics |
| jQuery 3.6.4 | JavaScript libraries |
| SvelteKit | UI frameworks |
| MySQL | Databases |
| PHP | Programming languages |
| Select2 | JavaScript libraries |
| DoubleClick Floodlight | Advertising |
| Google Ads Conversion Tracking | Analytics |
| Svelte | JavaScript frameworks |
| Unpkg | CDN |
| Vite | Miscellaneous |
| WordPress | CMS, Blogs |
| Cloudflare | CDN |
| Google Tag Manager | Tag managers |
| shadcn-svelte | UI frameworks |
| YouTube | Video players |
Web Application Vulnerabilities
Evidence
| Software / Version | Category |
|---|---|
| Google Ads | Advertising |
| TikTok Pixel | Analytics |
| Facebook Login | Authentication |
| Facebook Pixel 2.9.300 | Analytics |
| Fly.io | PaaS |
| Bootstrap | UI frameworks |
| core-js 3.32.2 | JavaScript libraries |
| Google Analytics GA4 | Analytics |
| jQuery 3.6.4 | JavaScript libraries |
| SvelteKit | UI frameworks |
| MySQL | Databases |
| PHP | Programming languages |
| Select2 | JavaScript libraries |
| DoubleClick Floodlight | Advertising |
| Google Ads Conversion Tracking | Analytics |
| Svelte | JavaScript frameworks |
| Unpkg | CDN |
| Vite | Miscellaneous |
| WordPress | CMS, Blogs |
| Cloudflare | CDN |
| Google Tag Manager | Tag managers |
| shadcn-svelte | UI frameworks |
| 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
| URL | Evidence |
|---|---|
| https://utmify.com.br/ | Response headers do not include the X-Content-Type-Options HTTP security header |
Vulnerability description
We noticed that the target application's server responses lack the X-Content-Type-Options header. This header is particularly important for preventing Internet Explorer from reinterpreting the content of a web page (MIME-sniffing) and thus overriding the value of the Content-Type header.
Risk description
The risk is that lack of this header could make possible attacks such as Cross-Site Scripting or phishing in Internet Explorer browsers.
Recommendation
We recommend setting the X-Content-Type-Options header such as `X-Content-Type-Options: nosniff`.
Classification
| CWE | CWE-693 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Evidence |
|---|---|
| https://utmify.com.br/ | Response headers do not include the HTTP Strict-Transport-Security header |
Vulnerability description
We noticed that the target application lacks the HTTP Strict-Transport-Security header in its responses. This security header is crucial as it instructs browsers to only establish secure (HTTPS) connections with the web server and reject any HTTP connections.
Risk description
The risk is that lack of this header permits an attacker to force a victim user to initiate a clear-text HTTP connection to the server, thus opening the possibility to eavesdrop on the network traffic and extract sensitive information (e.g. session cookies).
Recommendation
The Strict-Transport-Security HTTP header should be sent with each HTTPS response. The syntax is as follows: `Strict-Transport-Security: max-age=<seconds>[; includeSubDomains]` The parameter `max-age` gives the time frame for requirement of HTTPS in seconds and should be chosen quite high, e.g. several months. A value below 7776000 is considered as too low by this scanner check. The flag `includeSubDomains` defines that the policy applies also for sub domains of the sender of the response.
Classification
| CWE | CWE-693 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Evidence |
|---|---|
| https://utmify.com.br/ | 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 |
Evidence
| URL | Evidence |
|---|---|
| https://utmify.com.br/ | 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 | Summary |
|---|---|---|
| https://utmify.com.br/ | OPTIONS | We did a HTTP OPTIONS request. The server responded with a 204 status code and the header: `Allow: GET, HEAD, OPTIONS` Request / Response |
Vulnerability description
We have noticed that the webserver responded with an Allow HTTP header when an OPTIONS HTTP request was sent. This method responds to requests by providing information about the methods available for the target resource.
Risk description
The only risk this might present nowadays is revealing debug HTTP methods that can be used on the server. This can present a danger if any of those methods can lead to sensitive information, like authentication information, secret keys.
Recommendation
We recommend that you check for unused HTTP methods or even better, disable the OPTIONS method. This can be done using your webserver configuration.
Classification
| CWE | CWE-16 |
| 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
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| _dmarc.utmify.com.br | TXT | Text record | "v=DMARC1; p=none; rua=mailto:rua@dmarc.brevo.com,mailto:dmarc@utmify.com.br; ruf=mailto:dmarc@utmify.com.br; rf=afrf; pct=100" |
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 |
|---|---|---|---|
| rsa | 1296 | "k=rsa;p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDeMVIzrCa3T14JsNY0IRv5/2V1/v2itlviLQBwXsa7shBD6TrBkswsFUToPyMRWC9tbR/5ey0nRBH0ZVxp+lsmTxid2Y2z+FApQ6ra2VsXfbJP3HE6wAO0YTVEJt1TmeczhEd2Jiz/fcabIISgXEdSpTYJhb0ct0VJRxcg4c8c7wIDAQAB" |
Vulnerability description
We found that the DKIM record uses common selectors. The use of common DKIM selectors such as default, test, dkim, or mail may indicate a lack of proper customization or key management. Attackers often target domains using such selectors because they suggest that the domain is relying on default configurations, which could be less secure and easier to exploit. This can increase the risk of DKIM key exposure or misuse.
Risk description
Using a common DKIM selector makes it easier for attackers to predict and exploit email authentication weaknesses. Attackers may attempt to find corresponding DKIM keys or improperly managed records associated with common selectors. If a common selector is coupled with a weak key length or poor key management practices, it significantly increases the likelihood of email spoofing and phishing attacks.
Recommendation
We recommend using unique, customized selectors for each DKIM key to make it more difficult for attackers to predict and target the domain's DKIM records. Regularly rotate selectors and associated keys to further strengthen the security of your domain's email authentication infrastructure.
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| _dmarc.utmify.com.br | TXT | Text record | "v=DMARC1; p=none; rua=mailto:rua@dmarc.brevo.com,mailto:dmarc@utmify.com.br; ruf=mailto:dmarc@utmify.com.br; rf=afrf; pct=100" |
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 |
|---|---|---|---|
| utmify.com.br | SPF | Sender Policy Framework | "v=spf1 include:_spf.rdstation.com.br include:sendgrid.net ~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: lilyana.ns.cloudflare.com, piers.ns.cloudflare.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
| DKIM selector | Key type | Key size | Value |
|---|---|---|---|
| rsa | 1296 | "k=rsa;p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDeMVIzrCa3T14JsNY0IRv5/2V1/v2itlviLQBwXsa7shBD6TrBkswsFUToPyMRWC9tbR/5ey0nRBH0ZVxp+lsmTxid2Y2z+FApQ6ra2VsXfbJP3HE6wAO0YTVEJt1TmeczhEd2Jiz/fcabIISgXEdSpTYJhb0ct0VJRxcg4c8c7wIDAQAB" | |
| s1 | rsa | 1446 | "k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAyZu5IaVo9aN5EA6FKVoHgBa4LGVgsw4UVXX9UWtMmY1/fXqwzrTa3ZNH5A5d3Qiot1tZTLgftTQBapGY/RWJFQDVRfjfFMZ3+F7low8CRtI3AbE+tujLHX5lsgnrtEGM5KvSZiVG9AE9pHVvAqWF5RG4ZYMxRhBbWTaBSphHoRLb4DFLT/3Ujj6rcRihkmjjaS6Pg" "9njnYEuJU+0RfrI76LZg1z1r9z5z7px4yy4RCV2NEusBjPihUxMBxmbc80aN8MqeCnjFhfpqkXqAVU+615f8Ncnor+BuXFHmEdNradnajv8EsqfEMPaVUeINS1oZEhYdrzidXyhk1yO8upMaQIDAQAB" |
| s2 | rsa | 1446 | "k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAvGqGrCv107M1c67p4Pea+1IYFzkPYZSCGmXVBX6nj7EltyY9UHj6WO71p3bzo1E1AUQRnhfYVmaYtcG8uD2DVX5+GjMnvTDbTmaAAnEMYwROwGD97pNXmnE6ZNHBKH0RdYSKwqqGNmPUdww2SbHou10ehhLY+ddjlWXNL1PxU624tYQYUNCOCEGX6slZnpqD63OEN" "DNo2PrQo9kUzIkF8TWzKCSi3C+iROrVEpGkPGpMfnPvYZZPHyeMQ0zs6i/1VKRQhDniqtKrI13dDy3U80SqdvnVq6JOHGFin7VWUh5YyYsCCnSYl2qy7lBeP7/ST4NuoXbyMPHvcTeomSD6KwIDAQAB" |
Evidence
| Software / Version | Category |
|---|---|
| Cloudflare | 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 |
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 |
|---|---|
| WordPress | CMS, Blogs |
| MySQL | Databases |
| PHP | Programming languages |
| YouTube | Video players |
| Fly.io | PaaS |
| Google Ads | Advertising |
| Unpkg | CDN |
| Google Tag Manager | Tag managers |
| Google Analytics GA4 | Analytics |
| Google Ads Conversion Tracking | Analytics |
| Facebook Pixel 2.9.300 | Analytics |
| Cloudflare Browser Insights | Analytics, RUM |
| DoubleClick Floodlight | Advertising |
| Cloudflare | 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 |
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 |
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 11.1-STABLE | 91% |
Vulnerability description
OS Detection
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| utmify.com.br | A | IPv4 address | 104.26.11.205 |
| utmify.com.br | A | IPv4 address | 104.26.10.205 |
| utmify.com.br | A | IPv4 address | 172.67.68.221 |
| utmify.com.br | NS | Name server | lilyana.ns.cloudflare.com |
| utmify.com.br | NS | Name server | piers.ns.cloudflare.com |
| utmify.com.br | MX | Mail server | 1 smtp.google.com |
| utmify.com.br | SOA | Start of Authority | lilyana.ns.cloudflare.com. dns.cloudflare.com. 2399881483 10000 2400 604800 1800 |
| utmify.com.br | AAAA | IPv6 address | 2606:4700:20::681a:acd |
| utmify.com.br | AAAA | IPv6 address | 2606:4700:20::681a:bcd |
| utmify.com.br | AAAA | IPv6 address | 2606:4700:20::ac43:44dd |
| utmify.com.br | TXT | Text record | "brevo-code:f5f043a3222712a49ba4d9f0ff92626c" |
| utmify.com.br | TXT | Text record | "google-site-verification=4hpEtmIkEbsRWi-TfD2-NYFboSu_GmVDjRal6jOILog" |
| utmify.com.br | SPF | Sender Policy Framework | "v=spf1 include:_spf.rdstation.com.br include:sendgrid.net ~all" |
| utmify.com.br | CAA | Certificate Authority Authorization | 0 issue "amazon.com" |
| utmify.com.br | CAA | Certificate Authority Authorization | 0 issue "comodoca.com" |
| utmify.com.br | CAA | Certificate Authority Authorization | 0 issue "digicert.com; cansignhttpexchanges=yes" |
| utmify.com.br | CAA | Certificate Authority Authorization | 0 issue "letsencrypt.org" |
| utmify.com.br | CAA | Certificate Authority Authorization | 0 issue "pki.goog; cansignhttpexchanges=yes" |
| utmify.com.br | CAA | Certificate Authority Authorization | 0 issue "ssl.com" |
| utmify.com.br | CAA | Certificate Authority Authorization | 0 issuewild "amazon.com" |
| utmify.com.br | CAA | Certificate Authority Authorization | 0 issuewild "comodoca.com" |
| utmify.com.br | CAA | Certificate Authority Authorization | 0 issuewild "digicert.com; cansignhttpexchanges=yes" |
| utmify.com.br | CAA | Certificate Authority Authorization | 0 issuewild "letsencrypt.org" |
| utmify.com.br | CAA | Certificate Authority Authorization | 0 issuewild "pki.goog; cansignhttpexchanges=yes" |
| utmify.com.br | CAA | Certificate Authority Authorization | 0 issuewild "ssl.com" |
| _dmarc.utmify.com.br | TXT | Text record | "v=DMARC1; p=none; rua=mailto:rua@dmarc.brevo.com,mailto:dmarc@utmify.com.br; ruf=mailto:dmarc@utmify.com.br; rf=afrf; pct=100" |
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 |
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 |
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.