Vulnerability Scan Result
| Title: | Ampflower 🌺 |
| Description: | Converting tea into coffee-based code. |
| ip_address | 104.21.46.74 |
| country | - |
| network_name | Cloudflare Inc |
| asn | AS13335 |
| ip_address | 172.67.136.102 |
| 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 |
|---|---|
| HTTP/3 | Miscellaneous |
| Open Graph | Miscellaneous |
| Cloudflare | CDN |
| HSTS | Security |
Web Application Vulnerabilities
Evidence
| Software / Version | Category |
|---|---|
| HTTP/3 | Miscellaneous |
| Open Graph | Miscellaneous |
| Cloudflare | CDN |
| HSTS | Security |
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://ampflower.gay/ | 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 |
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
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.ampflower.gay | TXT | Text record | "v=DMARC1; p=reject; sp=reject; adkim=s; aspf=s; rua=mailto:c1caf25c3338444381c1327dccf62411@dmarc-reports.cloudflare.net,mailto:dmarc@ampflower.gay" |
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: walt.ns.cloudflare.com, annabel.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
| Operating System | Accuracy |
|---|---|
| Crestron XPanel control system | 91% |
Vulnerability description
OS Detection
Evidence
| Software / Version | Category |
|---|---|
| HSTS | Security |
| Cloudflare | CDN |
| HTTP/3 | Miscellaneous |
| Open Graph | 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 |
|---|---|
| HSTS | Security |
| Cloudflare | CDN |
| HTTP/3 | Miscellaneous |
| Open Graph | 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 |
|---|---|---|---|
| ampflower.gay | A | IPv4 address | 104.21.46.74 |
| ampflower.gay | A | IPv4 address | 172.67.136.102 |
| ampflower.gay | NS | Name server | walt.ns.cloudflare.com |
| ampflower.gay | NS | Name server | annabel.ns.cloudflare.com |
| ampflower.gay | MX | Mail server | 25 route1.mx.cloudflare.net |
| ampflower.gay | MX | Mail server | 41 route2.mx.cloudflare.net |
| ampflower.gay | MX | Mail server | 67 route3.mx.cloudflare.net |
| ampflower.gay | SOA | Start of Authority | annabel.ns.cloudflare.com. dns.cloudflare.com. 2386840901 10000 2400 604800 1800 |
| ampflower.gay | AAAA | IPv6 address | 2606:4700:3030::ac43:8866 |
| ampflower.gay | AAAA | IPv6 address | 2606:4700:3033::6815:2e4a |
| ampflower.gay | TXT | Text record | "google-site-verification=Mx81BLuNJh_QETUOYAKDhk32nVaLV4rZHa1hnj0zmbQ" |
| ampflower.gay | TXT | Text record | "keybase-site-verification=qpzYW9Gc8SO1uMozJ5E4A3snUKSwXgYyqDgynEmky6c" |
| ampflower.gay | SPF | Sender Policy Framework | "v=spf1 -all" |
| ampflower.gay | CAA | Certificate Authority Authorization | 0 issue "comodoca.com" |
| ampflower.gay | CAA | Certificate Authority Authorization | 0 issue "digicert.com; cansignhttpexchanges=yes" |
| ampflower.gay | CAA | Certificate Authority Authorization | 0 issue "letsencrypt.org" |
| ampflower.gay | CAA | Certificate Authority Authorization | 0 issue "pki.goog; cansignhttpexchanges=yes" |
| ampflower.gay | CAA | Certificate Authority Authorization | 0 issue "ssl.com" |
| ampflower.gay | CAA | Certificate Authority Authorization | 0 issuewild "comodoca.com" |
| ampflower.gay | CAA | Certificate Authority Authorization | 0 issuewild "digicert.com; cansignhttpexchanges=yes" |
| ampflower.gay | CAA | Certificate Authority Authorization | 0 issuewild "letsencrypt.org" |
| ampflower.gay | CAA | Certificate Authority Authorization | 0 issuewild "pki.goog; cansignhttpexchanges=yes" |
| ampflower.gay | CAA | Certificate Authority Authorization | 0 issuewild "ssl.com" |
| _dmarc.ampflower.gay | TXT | Text record | "v=DMARC1; p=reject; sp=reject; adkim=s; aspf=s; rua=mailto:c1caf25c3338444381c1327dccf62411@dmarc-reports.cloudflare.net,mailto:dmarc@ampflower.gay" |
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 |
|---|---|
| HSTS | Security |
| Cloudflare | CDN |
| HTTP/3 | Miscellaneous |
| Open Graph | 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 |
|---|---|---|---|
| ampflower.gay | SPF | Sender Policy Framework | "v=spf1 -all" |
Evidence
| Software / Version | Category |
|---|---|
| HSTS | Security |
| Cloudflare | CDN |
| HTTP/3 | Miscellaneous |
| Open Graph | 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.