Vulnerability Scan Result
| Title: | Gato Negro Capileira In Englsih |
| Description: | Holiday Home In Capoeira Granada Spain |
| ip_address | 172.66.0.70 |
| 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 Font API | Font scripts |
| Open Graph | Miscellaneous |
| Cloudflare | CDN |
Web Application Vulnerabilities
Evidence
| URL | Evidence |
|---|---|
| https://gatonegrocapileira.com/ | 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://gatonegrocapileira.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-693 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| Software / Version | Category |
|---|---|
| Google Font API | Font scripts |
| Open Graph | Miscellaneous |
| 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
| URL | Evidence |
|---|---|
| https://gatonegrocapileira.com/ | 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
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 | Evidence |
|---|---|
| https://gatonegrocapileira.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 |
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 | Summary |
|---|---|---|
| https://gatonegrocapileira.com/ | OPTIONS | We did a HTTP OPTIONS request. The server responded with a 200 status code and the header: `Allow: GET,POST,OPTIONS,HEAD` 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 |
Infrastructure Vulnerabilities
Evidence
We managed to extract the zone file from the ns2.site.nl name server.
Below are the first 5 lines of the zone file:
gatonegrocapileira.com. 3600 IN SOA ns1.site.eu. hostmaster.gatonegrocapileira.com. 2026021521 10800 3600 604800 3600 gatonegrocapileira.com. 3600 IN RRSIG SOA 13 2 3600 20260226000000 20260205000000 2257 gatonegrocapileira.com. QW1fjqB0H4VLzw7A/VMgYB263Nd8X/+GAEVI3dNrmCYZ79JqZJJVJCAn IYLMYADlL3dFoX98xFrfFW4tZmPbPw==
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 62900 ;; flags: qr aa; QUERY: 1, ANSWER: 29, AUTHORITY: 0, ADDITIONAL: 0
You can also see the entire zone file here.
Vulnerability description
The remote name server permits the execution of DNS zone transfers, a process that enables a malicious attacker to rapidly compile a list of potential targets. Furthermore, organizations frequently employ naming conventions that may inadvertently reveal a server's primary purpose, such as dev.example.com, staging.example.com, prod.example.com, and so forth.
Risk description
This data can be used by an attacker to gain insights about the network's structure and to find new potential targets.
Recommendation
Reconfigure the DNS server to only allow zone transfers from trusted IP addresses.
Evidence
We managed to extract the zone file from the ns4.site.de name server.
Below are the first 5 lines of the zone file:
gatonegrocapileira.com. 3600 IN SOA ns1.site.eu. hostmaster.gatonegrocapileira.com. 2026021521 10800 3600 604800 3600 gatonegrocapileira.com. 3600 IN RRSIG SOA 13 2 3600 20260226000000 20260205000000 2257 gatonegrocapileira.com. /2XjNA4mlGzgoyJU2FVR+gzryjooidcVpGEODuSIOosnuFy9T62V9/+L QSDPj13tQu/j/J5bNev/4Wmu086aUA==
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 24809 ;; flags: qr aa; QUERY: 1, ANSWER: 29, AUTHORITY: 0, ADDITIONAL: 0
You can also see the entire zone file here.
Vulnerability description
The remote name server permits the execution of DNS zone transfers, a process that enables a malicious attacker to rapidly compile a list of potential targets. Furthermore, organizations frequently employ naming conventions that may inadvertently reveal a server's primary purpose, such as dev.example.com, staging.example.com, prod.example.com, and so forth.
Risk description
This data can be used by an attacker to gain insights about the network's structure and to find new potential targets.
Recommendation
Reconfigure the DNS server to only allow zone transfers from trusted IP addresses.
Evidence
We managed to extract the zone file from the ns1.site.eu name server.
Below are the first 5 lines of the zone file:
gatonegrocapileira.com. 3600 IN SOA ns1.site.eu. hostmaster.gatonegrocapileira.com. 2026021521 10800 3600 604800 3600 gatonegrocapileira.com. 3600 IN RRSIG SOA 13 2 3600 20260226000000 20260205000000 2257 gatonegrocapileira.com. cUA88j8jQAb6+5vJ5dZHWi9PPkPCppIyQwlpjEf/J9h0v4bIfrxSRYIG OICaZOz+0BQSGANdpVpbTVbhI25K6A==
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 55209 ;; flags: qr aa; QUERY: 1, ANSWER: 29, AUTHORITY: 0, ADDITIONAL: 0
You can also see the entire zone file here.
Vulnerability description
The remote name server permits the execution of DNS zone transfers, a process that enables a malicious attacker to rapidly compile a list of potential targets. Furthermore, organizations frequently employ naming conventions that may inadvertently reveal a server's primary purpose, such as dev.example.com, staging.example.com, prod.example.com, and so forth.
Risk description
This data can be used by an attacker to gain insights about the network's structure and to find new potential targets.
Recommendation
Reconfigure the DNS server to only allow zone transfers from trusted IP addresses.
Evidence
We managed to extract the zone file from the ns3.site.be name server.
Below are the first 5 lines of the zone file:
gatonegrocapileira.com. 3600 IN SOA ns1.site.eu. hostmaster.gatonegrocapileira.com. 2026021521 10800 3600 604800 3600 gatonegrocapileira.com. 3600 IN RRSIG SOA 13 2 3600 20260226000000 20260205000000 2257 gatonegrocapileira.com. DWhNJ0eX/rR5XQKDVYMOAPj+w96f6aNgjmUwSLEx84Io8C8ge1IWpCxW Absy+YepdEbaHbNhfOH88h3eIkJR1Q==
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 29602 ;; flags: qr aa; QUERY: 1, ANSWER: 29, AUTHORITY: 0, ADDITIONAL: 0
You can also see the entire zone file here.
Vulnerability description
The remote name server permits the execution of DNS zone transfers, a process that enables a malicious attacker to rapidly compile a list of potential targets. Furthermore, organizations frequently employ naming conventions that may inadvertently reveal a server's primary purpose, such as dev.example.com, staging.example.com, prod.example.com, and so forth.
Risk description
This data can be used by an attacker to gain insights about the network's structure and to find new potential targets.
Recommendation
Reconfigure the DNS server to only allow zone transfers from trusted IP addresses.
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| _dmarc.gatonegrocapileira.com | TXT | Text record | "v=DMARC1; p=quarantine; sp=none; aspf=r; adkim=r; pct=100;" |
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
We found insecure DNS cookie usage on the following nameservers: ns1.site.eu, ns2.site.nl, ns3.site.be, ns4.site.de
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.gatonegrocapileira.com | TXT | Text record | "v=DMARC1; p=quarantine; sp=none; aspf=r; adkim=r; pct=100;" |
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
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.gatonegrocapileira.com | TXT | Text record | "v=DMARC1; p=quarantine; sp=none; aspf=r; adkim=r; pct=100;" |
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 |
|---|---|---|---|
| _dmarc.gatonegrocapileira.com | TXT | Text record | "v=DMARC1; p=quarantine; sp=none; aspf=r; adkim=r; pct=100;" |
Vulnerability description
We found that the target uses p=quarantine in the DMARC policy. When a DMARC policy is set to p=quarantine, emails that fail DMARC validation are delivered but placed in the recipient’s spam or junk folder. Although it offers some protection, this policy is less strict than p=reject, which blocks such emails entirely.
Risk description
While emails failing DMARC validation are sent to the spam folder, users may still retrieve them from there, leading to a higher risk of phishing and spoofing attacks succeeding. Moreover, less strict enforcement may allow more fraudulent emails to reach user inboxes if misclassified.
Recommendation
We recommend considering moving to a stricter policy, such as p=reject, where emails that fail DMARC validation are completely rejected rather than delivered to spam folders. This reduces the risk of users interacting with potentially malicious emails.
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| gatonegrocapileira.com | A | IPv4 address | 172.66.0.70 |
| gatonegrocapileira.com | NS | Name server | ns1.site.eu |
| gatonegrocapileira.com | NS | Name server | ns2.site.nl |
| gatonegrocapileira.com | NS | Name server | ns3.site.be |
| gatonegrocapileira.com | NS | Name server | ns4.site.de |
| gatonegrocapileira.com | MX | Mail server | 10 spamfilter1.site.eu |
| gatonegrocapileira.com | MX | Mail server | 20 spamfilter2.site.eu |
| gatonegrocapileira.com | SOA | Start of Authority | ns1.site.eu. hostmaster.gatonegrocapileira.com. 2026021521 10800 3600 604800 3600 |
| gatonegrocapileira.com | SPF | Sender Policy Framework | "v=spf1 include:_spf.site.eu -all" |
| _dmarc.gatonegrocapileira.com | TXT | Text record | "v=DMARC1; p=quarantine; sp=none; aspf=r; adkim=r; 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
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| gatonegrocapileira.com | SPF | Sender Policy Framework | "v=spf1 include:_spf.site.eu -all" |
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 |
|---|---|
| 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.0-RELEASE | 91% |
Vulnerability description
OS Detection