Vulnerability Scan Result
| Title: | Login |
| Description: | No description found |
| ip_address | 77.238.15.41 |
| country | IT  |
| network_name | Telecom Italia S.p.A. |
| asn | AS20746 |
25/tcp | smtp | - - |
80/tcp | http | IceWarp/13.0.3.13 x64 - |
110/tcp | pop3 | - - |
135/tcp | msrpc | Microsoft Windows RPC - |
139/tcp | netbios-ssn | Microsoft Windows netbios-ssn - |
143/tcp | imap | - - |
389/tcp | ldap | OpenLDAP 2.2.X - 2.3.X |
443/tcp | https | IceWarp/13.0.3.13 x64 - |
445/tcp | microsoft-ds | - - |
465/tcp | smtp | - - |
587/tcp | smtp | - - |
993/tcp | imap | - - |
995/tcp | pop3 | - - |
3306/tcp | mysql | - - |
5222/tcp | xmpp-client | ejabberd - |
5223/tcp | hpvirtgrp | - - |
| Software / Version | Category |
|---|---|
| PWA | Miscellaneous |
Web Application Vulnerabilities
Evidence
| URL | Evidence |
|---|---|
| https://mail.denver.sm/webmail/ | 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).
Evidence
| Software / Version | Category |
|---|---|
| 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.
Classification
| CWE | CWE-200 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Evidence |
|---|---|
| https://mail.denver.sm/webmail/ | 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
| URL | Evidence |
|---|---|
| https://mail.denver.sm/webmail/ | 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 |
Evidence
| URL | Evidence |
|---|---|
| https://mail.denver.sm/webmail/ | 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 |
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 |
Evidence
| URL | Evidence |
|---|---|
| https://mail.denver.sm/webmail/ |
|
Vulnerability description
We have discovered that the target application presents a login interface that could be a potential target for attacks. While login interfaces are standard for user authentication, they can become vulnerabilities if not properly secured.
Risk description
The risk is that an attacker could use this interface to mount brute force attacks against known passwords and usernames combinations leaked throughout the web.
Recommendation
Ensure each interface is not bypassable using common knowledge of the application or leaked credentials using occasional password audits.
Classification
| CWE | CWE-287 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Infrastructure Vulnerabilities
Evidence
We managed to detect a publicly accessible Windows Server Message Blocks (SMB) service. PORT STATE SERVICE VERSION 139/tcp open netbios-ssn Microsoft Windows netbios-ssn
Vulnerability description
We found that the Windows Server Message Blocks (SMB) service is publicly accessible. The Server Message Block (SMB) protocol facilitates services like file and print sharing on systems. Older SMB protocol versions operate through NetBIOS to enable application-layer networking for devices within Windows operating systems, including communication with printers and serial ports.
Risk description
Exposing this service online can enable attackers to launch authentication attacks, like guessing login credentials, potentially gaining unauthorized access. Attackers might use publicly available employee information for brute-force attacks. Vulnerabilities, such as unpatched software or protocol flaws, could also be exploited. An example is MS17-010 (EternalBlue) vulnerability. Additionally, integration with Active Directory Domain Services could allow attackers to move laterally across the network, accessing more systems and sensitive data.
Recommendation
We recommend turning off SMB access over the Internet and instead using a Virtual Private Network (VPN) that mandates two-factor authentication (2FA). Avoid permitting direct user authentication to Active Directory over the Internet to prevent attackers from engaging in password guessing or causing the lockout of legitimate domain user accounts. If the SMB service is essential for business purposes, we recommend limiting access only from designated IP addresses using a firewall.
Evidence
We managed to detect a publicly accessible Remote Procedure Call (RPC) service. PORT STATE SERVICE VERSION 135/tcp open msrpc Microsoft Windows RPC
Vulnerability description
We found that the Windows Remote Procedure Call (RPC) service is publicly accessible. RPC is a protocol that one program can use to request a service from a program located on another computer in a network.
Risk description
Exposing this service online can enable attackers to launch attacks, including unauthorized access, remote code execution, information disclosure, denial of service (DoS), and potential lateral movement within the network.
Recommendation
We recommend turning off RPC access over the Internet and instead using a Virtual Private Network (VPN) that mandates two-factor authentication (2FA). If the RPC service is essential for business purposes, we recommend limiting access only from designated IP addresses using a firewall.
Evidence
We managed to detect a publicly accessible Lightweight Directory Access Protocol (LDAP) service. PORT STATE SERVICE VERSION 389/tcp open ldap OpenLDAP 2.2.X - 2.3.X
Vulnerability description
We found that the Lightweight Directory Access Protocol (LDAP) service is publicly accessible. LDAP acts as a protocol for accessing information from Active Directory Directory Services, offering key insights such as directory services-related infrastructure data, user accounts, and more.
Risk description
Exposing this service online can enable attackers to extract information about the LDAP server. For instance, the ability to list user accounts from LDAP could aid an attacker in conducting password-based attacks against those users. Successfully breaching authentication could lead to gaining higher privileges or access to systems and resources.
Recommendation
We recommend turning off LDAP access over the Internet and instead using a Virtual Private Network (VPN) that mandates two-factor authentication (2FA). If the LDAP service is essential for business purposes, we recommend limiting access only from designated IP addresses using a firewall.
Evidence
We managed to detect a publicly accessible Post Office Protocol (POP3) service. Starting Nmap ( https://nmap.org ) at 2026-03-22 02:28 EET Nmap scan report for mail.denver.sm (77.238.15.41) Host is up (0.033s latency). rDNS record for 77.238.15.41: mail.studioleonardo.com
PORT STATE SERVICE VERSION
995/tcp open ssl/pop3
| fingerprint-strings:
| GenericLines:
| +OK mail.studioleonardo.com Studio Leonardo Network POP3 Sun, 22 Mar 2026 01:28:58 +0100
| -ERR Command unrecognized: ""
| -ERR Command unrecognized: ""
| HTTPOptions:
| +OK mail.studioleonardo.com Studio Leonardo Network POP3 Sun, 22 Mar 2026 01:29:09 +0100
| -ERR Command unrecognized: "OPTIONS / HTTP/1.0"
| -ERR Command unrecognized: ""
| NULL:
|_ +OK mail.studioleonardo.com Studio Leonardo Network POP3 Sun, 22 Mar 2026 01:28:58 +0100
|_pop3-capabilities: USER UIDL APOP EXPIRE(NEVER) TOP SASL(PLAIN LOGIN DIGEST-MD5 CRAM-MD5)
1 service unrecognized despite returning data. If you know the service/version, please submit the following fingerprint at https://nmap.org/cgi-bin/submit.cgi?new-service :
SF-Port995-TCP:V=7.93%T=SSL%I=7%D=3/22%Time=69BF37D0%P=x86_64-pc-linux-gnu
SF:%r(NULL,83,"+OK\x20mail.studioleonardo.com\x20Studio\x20Leonardo\x20
SF:Network\x20POP3\x20Sun,\x2022\x20Mar\x202026\x2001:28:58\x20+0100\x20<
SF:20260322012858@mail.studioleonardo.com>\r\n")%r(GenericLines,C1,"+OK
SF:\x20mail.studioleonardo.com\x20Studio\x20Leonardo\x20Network\x20POP3
SF:x20Sun,\x2022\x20Mar\x202026\x2001:28:58\x20+0100\x20\r\n-ERR\x20Command\x20unrecognized:\x20""\r
SF:\n-ERR\x20Command\x20unrecognized:\x20""\r\n")%r(HTTPOptions,D3,"+OK
SF:\x20mail.studioleonardo.com\x20Studio\x20Leonardo\x20Network\x20POP3
SF:x20Sun,\x2022\x20Mar\x202026\x2001:29:09\x20+0100\x20\r\n-ERR\x20Command\x20unrecognized:\x20"OPTI
SF:ONS\x20/\x20HTTP/1.0"\r\n-ERR\x20Command\x20unrecognized:\x20""\r\n
SF:");
Service detection performed. Please report any incorrect results at https://nmap.org/submit/ . Nmap done: 1 IP address (1 host up) scanned in 22.94 seconds
Vulnerability description
We found that the Post Office Protocol (POP3) service is publicly accessible and doesn’t include STARTTLS capability. Email clients use the Post Office Protocol (POP) to download emails for user accounts. Some POP servers are initially set up to operate over an unsecured protocol. When email clients download email content through this plaintext protocol, it can pose a substantial risk to the organization's network, especially depending on which user account is set to receive the emails.
Risk description
Exposing this service online can enable attackers to conduct man-in-the-middle attacks, thereby gaining access to sensitive user credentials and the contents of emails. Given that POP3 operates via a plaintext protocol, the entirety of the data exchanged between the client and server is left unencrypted. This critical information could then be leveraged in further attacks on the organization's network.
Recommendation
We recommend turning off POP3 access over the Internet and instead using a Virtual Private Network (VPN) that mandates two-factor authentication (2FA). If the POP3 service is essential for business purposes, we recommend limiting access only from designated IP addresses using a firewall. Furthermore, activating STARTTLS capability (switching the connection to a secure communication) or utilizing Secure POP3 (POP3S) is recommended, as this protocol employs encryption.
Evidence
| Operating System | Accuracy |
|---|---|
| Microsoft Windows Server 2016 | 92% |
Vulnerability description
OS Detection
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| mail.denver.sm | A | IPv4 address | 77.238.15.41 |
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.