Vulnerability Scan Result
| Title: | 403 Forbidden |
| Description: | No description found |
| ip_address | 157.90.182.9 |
| country | DE  |
| network_name | Hetzner Online GmbH |
| asn | AS24940 |
80/tcp | http | nginx - |
443/tcp | https | nginx - |
9999/tcp | https | - - |
| Software / Version | Category |
|---|---|
| Nginx | Web servers, Reverse proxies |
Web Application Vulnerabilities
Evidence
| URL | Response URL | Evidence |
|---|---|---|
| http://www.branvity.pl/ | http://www.branvity.pl/ | Communication is made over unsecure, unencrypted HTTP. |
Vulnerability description
We noticed that the communication between the web browser and the server is done using the HTTP protocol, which transmits data unencrypted over the network.
Risk description
The risk is that an attacker who manages to intercept the communication at the network level can read and modify the data transmitted (including passwords, secret tokens, credit card information and other sensitive data).
Recommendation
We recommend you to reconfigure the web server to use HTTPS - which encrypts the communication between the web browser and the server.
Classification
| CWE | CWE-311 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| Software / Version | Category |
|---|---|
| Nginx | Web servers, Reverse proxies |
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.
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.
Infrastructure Vulnerabilities
Evidence
| Operating System | Accuracy |
|---|---|
| Linux 4.15 - 5.6 | 100% |
Vulnerability description
OS Detection
Evidence
| Software / Version | Category |
|---|---|
| Nginx | Web servers, Reverse proxies |
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 |
|---|---|
| Nginx | Web servers, Reverse proxies |
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 |
|---|---|---|---|
| www.branvity.pl | A | IPv4 address | 157.90.182.9 |
| www.branvity.pl | NS | Name server | dns1.mydevil.net |
| www.branvity.pl | NS | Name server | dns2.mydevil.net |
| www.branvity.pl | MX | Mail server | 10 mail14.mydevil.net |
| www.branvity.pl | SOA | Start of Authority | dns1.mydevil.net. admin.admin.net.pl. 2025130004 10800 3600 604800 10800 |
| www.branvity.pl | TXT | Text record | "google-site-verification=KVP8EPw0iC9GPSkRZ0jPyMy1TuocwjmBu-RuUNBk2vE" |
| www.branvity.pl | TXT | Text record | "facebook-domain-verification=9izrr076xpp24ppovnqs7t4fq6a1ct" |
| www.branvity.pl | SPF | Sender Policy Framework | "v=spf1 mx a include:mail14.mydevil.net -all" |
| www.branvity.pl | CNAME | Canonical name | branvity.pl |
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.