Vulnerability Scan Result
| Title: | Онлайн библиотека LoveRead.me – читать книги онлайн бесплатно |
| Description: | Онлайн библиотека LoveRead.me – тысячи книг для бесплатного чтения без регистрации. Удобный поиск по жанрам и авторам. |
| ip_address | 185.43.220.24 |
| country | NL  |
| network_name | WIBO Baltic UAB |
| asn | AS59939 |
53/tcp | domain | ISC BIND 9.18.49-1~deb12u1 |
80/tcp | http | nginx - |
443/tcp | https | nginx - |
8000/tcp | http | Cowboy httpd - |
| Software / Version | Category |
|---|---|
| Nginx | Web servers, Reverse proxies |
| PHP | Programming languages |
| Plausible | Analytics |
| PWA | Miscellaneous |
| HSTS | Security |
Web Application Vulnerabilities
Evidence
| Software / Version | Category |
|---|---|
| Nginx | Web servers, Reverse proxies |
| PHP | Programming languages |
| Plausible | Analytics |
| PWA | Miscellaneous |
| 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.
Classification
| CWE | CWE-200 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Evidence |
|---|---|
| https://loveread.me/ | 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://loveread.me/ | 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
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).
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
We managed to extract the zone file from the ns2.loveread.me name server.
Below are the first 5 lines of the zone file:
loveread.me. 3600 IN SOA server20023.loveread.ec. loveread.library.gmail.com. 2026020217 10800 3600 604800 86400 loveread.me. 3600 IN NS ns1.loveread.me. loveread.me. 3600 IN NS ns2.loveread.me. loveread.me. 3600 IN TXT "v=spf1 ip4:185.43.220.24 ip4:185.43.221.166 a mx ~all" loveread.me. 3600 IN TXT "google-site-verification=b9txSpMhiE64VPi6Hsyx4a4kWdYQqKCW_lU5TkSSD88"
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.loveread.me name server.
Below are the first 5 lines of the zone file:
loveread.me. 3600 IN SOA server20023.loveread.ec. loveread.library.gmail.com. 2026020217 10800 3600 604800 86400 loveread.me. 3600 IN NS ns1.loveread.me. loveread.me. 3600 IN NS ns2.loveread.me. loveread.me. 3600 IN TXT "v=spf1 ip4:185.43.220.24 ip4:185.43.221.166 a mx ~all" loveread.me. 3600 IN TXT "google-site-verification=b9txSpMhiE64VPi6Hsyx4a4kWdYQqKCW_lU5TkSSD88"
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 |
|---|---|---|---|
| loveread.me | SPF | Sender Policy Framework | "v=spf1 ip4:185.43.220.24 ip4:185.43.221.166 a mx ~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
| Operating System | Accuracy |
|---|---|
| HP P2000 G3 NAS device | 93% |
Vulnerability description
OS Detection
Evidence
| Software / Version | Category |
|---|---|
| PHP | Programming languages |
| Nginx | Web servers, Reverse proxies |
| Plausible | Analytics |
| HSTS | Security |
| PWA | 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 |
|---|---|
| Erlang | Programming languages |
| Cowboy | Web servers |
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 |
|---|---|---|---|
| loveread.me | A | IPv4 address | 185.43.220.24 |
| loveread.me | NS | Name server | ns1.loveread.me |
| loveread.me | NS | Name server | ns2.loveread.me |
| loveread.me | SOA | Start of Authority | server20023.loveread.ec. loveread.library.gmail.com. 2026020217 10800 3600 604800 86400 |
| loveread.me | TXT | Text record | "google-site-verification=b9txSpMhiE64VPi6Hsyx4a4kWdYQqKCW_lU5TkSSD88" |
| loveread.me | SPF | Sender Policy Framework | "v=spf1 ip4:185.43.220.24 ip4:185.43.221.166 a mx ~all" |
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.