Vulnerability Scan Result
| Title: | Swagger UI |
| Description: | No description found |
| ip_address | 145.239.200.29 |
| country | FR  |
| network_name | Ovh Sas |
| asn | AS16276 |
21/tcp | ftp | Microsoft ftpd - |
80/tcp | http | Microsoft IIS httpd 10 |
135/tcp | msrpc | Microsoft Windows RPC - |
139/tcp | netbios-ssn | Microsoft Windows netbios-ssn - |
443/tcp | https | - - |
445/tcp | microsoft-ds | - - |
1433/tcp | ms-sql-s | Microsoft SQL Server - |
3389/tcp | ms-wbt-server | Microsoft Terminal Services - |
5357/tcp | http | Microsoft HTTPAPI httpd 2 |
5985/tcp | http | Microsoft HTTPAPI httpd 2 |
7070/tcp | realserver | - - |
| Software / Version | Category |
|---|---|
| Kestrel | Web servers |
| core-js 3.20.3 | JavaScript libraries |
| Google Font API | Font scripts |
| React | JavaScript frameworks |
| Swagger UI 4.15.5 | Documentation |
| Microsoft ASP.NET | Web frameworks |
Web Application Vulnerabilities
Evidence
| URL | Response URL | Evidence |
|---|---|---|
| http://backend-dev.ecomminds.co.uk/swagger | http://backend-dev.ecomminds.co.uk/swagger/index.html | 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
| URL | Evidence |
|---|---|
| http://backend-dev.ecomminds.co.uk/swagger | 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
| Software / Version | Category |
|---|---|
| Kestrel | Web servers |
| core-js 3.20.3 | JavaScript libraries |
| Google Font API | Font scripts |
| React | JavaScript frameworks |
| Swagger UI 4.15.5 | Documentation |
| Microsoft ASP.NET | Web frameworks |
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 |
|---|---|
| http://backend-dev.ecomminds.co.uk/swagger | 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.
Infrastructure Vulnerabilities
Evidence
We managed to detect a publicly accessible Remote Desktop Protocol (RDP) service. PORT STATE SERVICE VERSION 3389/tcp open ms-wbt-server Microsoft Terminal Services
Vulnerability description
We found that the Remote Desktop Protocol (RDP) service is publicly accessible. Attackers often look for the Remote Desktop Protocol service due to its capability to provide remote access and control of a server, usually one that operates on the Microsoft Windows operating system.
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 CVE-2019-0708 (Bluekeep) 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 Remote Desktop Protocol 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 Remote Desktop Protocol service is essential for business purposes, limiting access to designated IP addresses is recommended.
Evidence
We managed to detect a publicly accessible Windows Microsoft SQL Server (MSSQL) service. PORT STATE SERVICE VERSION 1433/tcp open ms-sql-s Microsoft SQL Server
Vulnerability description
We found that the Microsoft SQL Server (MSSQL) is publicly accessible. This service often holds critical organizational data, making it a potential prime target for determined attackers.
Risk description
The risk exists that an attacker exploits this issue by launching a password-based attack on the MSSQL service. If an attacker identifies a correct set of login details, they could gain access to the database and start enumerating, potentially revealing confidential information. Moreover, such vulnerabilities could lead to other forms of attacks, including privilege escalation, allowing attackers to run system commands and move laterally to other systems in the internal network.
Recommendation
We recommend ensuring that the Microsoft SQL Server (MSSQL) service is not publicly accessible. The MSSQL service should be safeguarded behind a firewall or made available only to users connected through a Virtual Private Network (VPN) server. However, if the MSSQL service is required to be directly accessible over the Internet, we recommend reconfiguring it such that it is accessible only from known IP addresses.
Evidence
We managed to detect a publicly accessible Windows Remote Management (WinRM) service. PORT STATE SERVICE VERSION 5985/tcp open http Microsoft HTTPAPI httpd 2.0
Vulnerability description
We found that the Windows Remote Management (WinRM) service is publicly accessible. Network administrators often use remote administration protocols to control devices like servers and other essential systems. However, allowing these services to be accessible from the Internet can increase security risks, creating potential opportunities for attacks on the organization. Also, it operates in cleartext, making all traffic communicated through this protocol vulnerable to interception in its unencrypted form.
Risk description
Exposing this service online can enable attackers to launch authentication attacks, like guessing login credentials, and potentially gaining unauthorized access. Also, any vulnerabilities in the WinRM service or the underlying Windows OS can be exploited by attackers to gain access or elevate privileges. Given the high privilege level of WinRM, exploiting such vulnerabilities can lead to full system compromise This could also lead to the exposure of sensitive data such as user credentials and other sensitive information depending on the device being managed remotely since it uses a cleartext transfer of data. If an attacker intercepts these credentials, they might gain unauthorized access to the device.
Recommendation
We recommend turning off WinRM access over the Internet and instead using a Virtual Private Network (VPN) that mandates two-factor authentication (2FA). If the WinRM service is essential for business purposes, we recommend limiting access only from designated IP addresses using a firewall. Furthermore, utilizing HTTPS with WinRM (port 5986) is recommended as this protocol employs encryption.
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 File Transfer Protocol (FTP) service. PORT STATE SERVICE VERSION 21/tcp open ftp Microsoft ftpd
Vulnerability description
We found that the File Transfer Protocol (FTP) service is publicly accessible. The FTP enables client systems to connect to upload and download files. Nonetheless, FTP lacks encryption for the data exchanged between the server and the client, leaving all transferred data exposed in plaintext.
Risk description
Exposing this service online can enable attackers to execute man-in-the-middle attacks, capturing sensitive user credentials and the contents of files because FTP operates without encryption. The entirety of the communication between the client and the server remains unsecured in plaintext. This acquired information could further facilitate additional attacks within the network.
Recommendation
We recommend turning off FTP access over the Internet and instead using a Virtual Private Network (VPN) that mandates two-factor authentication (2FA). If the FTP service is essential for business purposes, we recommend limiting access only from designated IP addresses using a firewall. Furthermore, utilizing SFTP (Secure File Transfer Protocol) is recommended as this protocol employs encryption to secure data transfers.
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
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| backend-dev.ecomminds.co.uk | A | IPv4 address | 145.239.200.29 |
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 |
|---|---|
| Swagger UI | Documentation |
| Microsoft ASP.NET | Web frameworks |
| Kestrel | 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
| Software / Version | Category |
|---|---|
| Microsoft HTTPAPI 2.0 | 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
| Software / Version | Category |
|---|---|
| Microsoft HTTPAPI 2.0 | 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
| Operating System | Accuracy |
|---|---|
| Microsoft Windows Server 2016 | 92% |
Vulnerability description
OS Detection
Evidence
| Software / Version | Category |
|---|---|
| Swagger UI | Documentation |
| Microsoft ASP.NET | Web frameworks |
| Kestrel | 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.