Vulnerability Scan Result
| Title: | Attention Required! | Cloudflare |
| Description: | No description found |
| IP address | 104.22.66.191 |
| Country | - |
| AS number | AS13335 |
| Net name | Cloudflare Inc |
| IP address | 104.22.67.191 |
| Country | - |
| AS number | AS13335 |
| Net name | Cloudflare Inc |
| IP address | 172.67.12.243 |
| Country | - |
| AS number | AS13335 |
| Net name | Cloudflare Inc |
80/tcp | http | Cloudflare http proxy - |
443/tcp | https | cloudflare - |
8080/tcp | http | Cloudflare http proxy - |
8443/tcp | http | cloudflare - |
| Software / Version | Category |
|---|---|
| Cloudflare | CDN |
Web Application Vulnerabilities
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.
Classification
| OWASP Top 10 - 2017 | A6 - Security Misconfiguration |
| OWASP Top 10 - 2021 | A5 - Security Misconfiguration |
Evidence
Vulnerability description
Website is accessible.
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
| OWASP Top 10 - 2017 | A6 - Security Misconfiguration |
| OWASP Top 10 - 2021 | A5 - Security Misconfiguration |
Infrastructure Vulnerabilities
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| _dmarc.epravda.com.ua | TXT | Text record | "v=DMARC1; p=quarantine; sp=quarantine; pct=100; rua=mailto:yo3jtsbv@ag.eu.dmarcian.com; ruf=mailto:yo3jtsbv@fr.eu.dmarcian.com; fo=1; aspf=s; adkim=s;" |
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 |
|---|---|---|---|
| epravda.com.ua | A | IPv4 address | 104.22.66.191 |
| epravda.com.ua | A | IPv4 address | 104.22.67.191 |
| epravda.com.ua | A | IPv4 address | 172.67.12.243 |
| epravda.com.ua | NS | Name server | elsa.ns.cloudflare.com |
| epravda.com.ua | NS | Name server | tim.ns.cloudflare.com |
| epravda.com.ua | MX | Mail server | 10 aspmx.l.google.com |
| epravda.com.ua | MX | Mail server | 20 alt1.aspmx.l.google.com |
| epravda.com.ua | MX | Mail server | 20 alt2.aspmx.l.google.com |
| epravda.com.ua | MX | Mail server | 30 aspmx2.googlemail.com |
| epravda.com.ua | MX | Mail server | 30 aspmx3.googlemail.com |
| epravda.com.ua | MX | Mail server | 30 aspmx4.googlemail.com |
| epravda.com.ua | MX | Mail server | 30 aspmx5.googlemail.com |
| epravda.com.ua | SOA | Start of Authority | elsa.ns.cloudflare.com. dns.cloudflare.com. 2367861655 10000 2400 604800 1800 |
| epravda.com.ua | AAAA | IPv6 address | 2606:4700:10::6816:43bf |
| epravda.com.ua | AAAA | IPv6 address | 2606:4700:10::6816:42bf |
| epravda.com.ua | AAAA | IPv6 address | 2606:4700:10::ac43:cf3 |
| epravda.com.ua | TXT | Text record | "google-site-verification=1SATIY2lXKtA2BlHPUeEjT3UXQm9zbT200PbD9o5mYU" |
| epravda.com.ua | SPF | Sender Policy Framework | "v=spf1 include:_spf.google.com -all" |
| epravda.com.ua | CAA | Certificate Authority Authorization | 0 iodef "mailto:webmaster@pravda.com.ua" |
| epravda.com.ua | CAA | Certificate Authority Authorization | 0 issue "comodoca.com" |
| epravda.com.ua | CAA | Certificate Authority Authorization | 0 issue "digicert.com; cansignhttpexchanges=yes" |
| epravda.com.ua | CAA | Certificate Authority Authorization | 0 issue "letsencrypt.org" |
| epravda.com.ua | CAA | Certificate Authority Authorization | 0 issue "pki.goog; cansignhttpexchanges=yes" |
| epravda.com.ua | CAA | Certificate Authority Authorization | 0 issue "ssl.com" |
| epravda.com.ua | CAA | Certificate Authority Authorization | 0 issuewild "comodoca.com" |
| epravda.com.ua | CAA | Certificate Authority Authorization | 0 issuewild "digicert.com; cansignhttpexchanges=yes" |
| epravda.com.ua | CAA | Certificate Authority Authorization | 0 issuewild "letsencrypt.org" |
| epravda.com.ua | CAA | Certificate Authority Authorization | 0 issuewild "pki.goog; cansignhttpexchanges=yes" |
| epravda.com.ua | CAA | Certificate Authority Authorization | 0 issuewild "ssl.com" |
| _dmarc.epravda.com.ua | TXT | Text record | "v=DMARC1; p=quarantine; sp=quarantine; pct=100; rua=mailto:yo3jtsbv@ag.eu.dmarcian.com; ruf=mailto:yo3jtsbv@fr.eu.dmarcian.com; fo=1; aspf=s; adkim=s;" |
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
Vulnerability description
OS detection couldn't determine the operating system.
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| epravda.com.ua | SPF | Sender Policy Framework | "v=spf1 include:_spf.google.com -all" |
Evidence
| DKIM selector | Key type | Key size | Value |
|---|---|---|---|
| rsa | 1422 | "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAkW1635dGtKe5J0oY/QNduOlbg+jvfvgLg1EiL55Ay2InRvuapM4CPmcBqH/SaJpK1Etwc4kI1G8TDEG1Out4CiX3ET+sZ4JZeJ3WKoaSsiOC4g5KhKuf9ShTVMX5n6qKwVBo9eFlIndNcVquWgiJ7jazWasFkG9TIw3z/rM8759Wj8N12/uEVIEfaec4i3pay" "2Epd9lrEPqX1kganr8owD7O3DA+knPaYVp/ShLNUKwZdqkzkcfZK2OCdh9fJtgmvpzUkoaJ+s2jNYjOwjBBUIzKhAg250SA8stI972Exp8P+8FkZV6eAkzXpAPZtDfUCH+ISzvVxQZxXVm08lWOPwIDAQAB" |
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.