Vulnerability Scan Result

Target:

https://www.proteinbank.it/ (redirect)

Scanned target: https://proteinbank.it/

Submitted: April 17, 2025 from DE

Public Scan

Scan mode: Passive (non-intrusive)

Summary

medium

Info

Low

Medium

High

Critical

Screenshot

Title:	Home – Protein Bank
Description:

IP Information

IP address	138.201.139.240
Country	DE
AS number	AS24940
Net name	Hetzner Online GMBH

Open Ports

21/tcp	ftp	ProFTPD -
22/tcp	ssh	OpenSSH 8.2p1 Ubuntu 4ubuntu0.3
25/tcp	smtp	Postfix smtpd -
53/tcp	domain	- -
80/tcp	http	nginx -
106/tcp	tcpwrapped	- -
110/tcp	pop3	Dovecot pop3d -
143/tcp	imap	Dovecot imapd -
443/tcp	https	nginx -
465/tcp	smtp	Postfix smtpd -
993/tcp	imap	Dovecot imapd -
995/tcp	pop3	Dovecot pop3d -
3306/tcp	mysql	MySQL 5.5.5-10.3.34-MariaDB-0ubuntu0.20.04.1
8443/tcp	https	sw-cp-server -

Web Technologies

Software / Version	Category
Contact Form 7 6.0.6	WordPress plugins, Form builders
Magnific Popup 1.0	JavaScript libraries
Envo eCommerce 1.2.1	WordPress themes
FancyBox 3.5.7	JavaScript libraries
Font Awesome	Font scripts
Bootstrap	UI frameworks
jQuery Migrate 3.4.1	JavaScript libraries
Google Font API	Font scripts
jQuery	JavaScript libraries
Yandex.Metrika	Analytics
MySQL	Databases
Nginx	Web servers, Reverse proxies
Open Graph	Miscellaneous
PHP 7.4.33	Programming languages
RankMath SEO	WordPress plugins, SEO
Twitter Emoji (Twemoji)	Font scripts
WooCommerce 9.8.1	Ecommerce, WordPress plugins
WordPress 6.7.2	CMS, Blogs
jsDelivr	CDN
RSS	Miscellaneous
Cart Functionality	Ecommerce
WhatsApp Business Chat	Live chat

Web Application Vulnerabilities

Evidence

URL	Cookie Name	Evidence
https://proteinbank.it/	mc_session_ids[multi][0], mc_session_ids[multi][1], mc_session_ids[multi][2], mc_session_ids[multi][3], mc_session_ids[multi][4]	The server responded with Set-Cookie header(s) that does not specify the HttpOnly flag: Set-Cookie: mc_session_ids[multi][0]=26eb229fe87fd16f9717e300edbea1608c6b59c1 Set-Cookie: mc_session_ids[multi][1]=eb2db14c484f0c3a11a12c7fa6e6def5c1d8c852 Set-Cookie: mc_session_ids[multi][2]=a62b95ad54eadd587f21b7536bbe4eab9a8d862a Set-Cookie: mc_session_ids[multi][3]=8873e513b5e17469ae5ed29776d388561cc17c8c Set-Cookie: mc_session_ids[multi][4]=7b80c3505caa0de66bf3f39209cc34658c23c8c5

Vulnerability description

We found that a cookie has been set without the HttpOnly flag, which means it can be accessed by potentially malicious JavaScript code running inside the web page. The root cause for this usually revolves around misconfigurations in the code or server settings.

Risk description

The risk is that an attacker who injects malicious JavaScript code on the page (e.g. by using an XSS attack) can access the cookie and can send it to another site. In case of a session cookie, this could lead to session hijacking.

Recommendation

Ensure that the HttpOnly flag is set for all cookies.

Classification

CWE	CWE-1004
OWASP Top 10 - 2017	A6 - Security Misconfiguration
OWASP Top 10 - 2021	A5 - Security Misconfiguration

Evidence

URL	Cookie Name	Evidence
https://proteinbank.it/	mc_session_ids[multi][0], mc_session_ids[multi][1], mc_session_ids[multi][2], mc_session_ids[multi][3], mc_session_ids[multi][4]	Set-Cookie: mc_session_ids[multi][0]=26eb229fe87fd16f9717e300edbea1608c6b59c1 Set-Cookie: mc_session_ids[multi][1]=eb2db14c484f0c3a11a12c7fa6e6def5c1d8c852 Set-Cookie: mc_session_ids[multi][2]=a62b95ad54eadd587f21b7536bbe4eab9a8d862a Set-Cookie: mc_session_ids[multi][3]=8873e513b5e17469ae5ed29776d388561cc17c8c Set-Cookie: mc_session_ids[multi][4]=7b80c3505caa0de66bf3f39209cc34658c23c8c5

Vulnerability description

We found that a cookie has been set without the Secure flag, which means the browser will send it over an unencrypted channel (plain HTTP) if such a request is made. The root cause for this usually revolves around misconfigurations in the code or server settings.

Risk description

The risk exists that an attacker will intercept the clear-text communication between the browser and the server and he will steal the cookie of the user. If this is a session cookie, the attacker could gain unauthorized access to the victim's web session.

Recommendation

Whenever a cookie contains sensitive information or is a session token, then it should always be passed using an encrypted channel. Ensure that the secure flag is set for cookies containing such sensitive information.

Classification

CWE	CWE-614
OWASP Top 10 - 2017	A6 - Security Misconfiguration
OWASP Top 10 - 2021	A5 - Security Misconfiguration

Evidence

Risk Level	CVSS	CVE	Summary	Affected software
	6.2	CVE-2022-4900	A vulnerability was found in PHP where setting the environment variable PHP_CLI_SERVER_WORKERS to a large value leads to a heap buffer overflow.	php 7.4.33
	5.3	CVE-2024-5458	In PHP versions 8.1.* before 8.1.29, 8.2.* before 8.2.20, 8.3.* before 8.3.8, due to a code logic error, filtering functions such as filter_var when validating URLs (FILTER_VALIDATE_URL) for certain types of URLs the function will result in invalid user information (username + password part of URLs) being treated as valid user information. This may lead to the downstream code accepting invalid URLs as valid and parsing them incorrectly.	php 7.4.33

Vulnerability description

We noticed known vulnerabilities in the target application based on the server responses. They are usually related to outdated systems and expose the affected applications to the risk of unauthorized access to confidential data and possibly denial of service attacks. Depending on the system distribution the affected software can be patched but displays the same version, requiring manual checking.

Risk description

The risk is that an attacker could search for an appropriate exploit (or create one himself) for any of these vulnerabilities and use it to attack the system.

Recommendation

In order to eliminate the risk of these vulnerabilities, we recommend you check the installed software version and upgrade to the latest version.

Classification

CWE	CWE-1026
OWASP Top 10 - 2017	A9 - Using Components with Known Vulnerabilities
OWASP Top 10 - 2021	A6 - Vulnerable and Outdated Components

Evidence

URL	Evidence
https://proteinbank.it/	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	A6 - Security Misconfiguration
OWASP Top 10 - 2021	A5 - Security Misconfiguration

Evidence

URL	Evidence
https://proteinbank.it/	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	A6 - Security Misconfiguration
OWASP Top 10 - 2021	A5 - Security Misconfiguration

Evidence

URL	Evidence
https://proteinbank.it/	Response headers do not include the Referrer-Policy HTTP security header as well as the `<meta/>` tag with name 'referrer' is not present in the response.

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	A6 - Security Misconfiguration
OWASP Top 10 - 2021	A5 - Security Misconfiguration

Evidence

URL	Evidence
https://proteinbank.it/	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	A6 - Security Misconfiguration
OWASP Top 10 - 2021	A5 - Security Misconfiguration

Evidence

Software / Version	Category
Contact Form 7 6.0.6	WordPress plugins, Form builders
Magnific Popup 1.0	JavaScript libraries
Envo eCommerce 1.2.1	WordPress themes
FancyBox 3.5.7	JavaScript libraries
Font Awesome	Font scripts
Bootstrap	UI frameworks
jQuery Migrate 3.4.1	JavaScript libraries
Google Font API	Font scripts
jQuery	JavaScript libraries
Yandex.Metrika	Analytics
MySQL	Databases
Nginx	Web servers, Reverse proxies
Open Graph	Miscellaneous
PHP 7.4.33	Programming languages
RankMath SEO	WordPress plugins, SEO
Twitter Emoji (Twemoji)	Font scripts
WooCommerce 9.8.1	Ecommerce, WordPress plugins
WordPress 6.7.2	CMS, Blogs
jsDelivr	CDN
RSS	Miscellaneous
Cart Functionality	Ecommerce
WhatsApp Business Chat	Live chat

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

URL
https://proteinbank.it/robots.txt

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).

Classification

OWASP Top 10 - 2017	A6 - Security Misconfiguration
OWASP Top 10 - 2021	A5 - Security Misconfiguration

Evidence

URL
Missing: https://proteinbank.it/.well-known/security.txt

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

We managed to detect a publicly accessible SSH service.

Starting Nmap ( https://nmap.org ) at 2025-04-17 08:44 EEST
Nmap scan report for www.proteinbank.it (138.201.139.240)
Host is up (0.020s latency).
rDNS record for 138.201.139.240: static.240.139.201.138.clients.your-server.de

PORT   STATE SERVICE VERSION
22/tcp open  ssh     OpenSSH 8.2p1 Ubuntu 4ubuntu0.3 (Ubuntu Linux; protocol 2.0)
| ssh-auth-methods: 
|   Supported authentication methods: 
|     publickey
|_    password
Service Info: OS: Linux; CPE: cpe:/o:linux:linux_kernel

Service detection performed. Please report any incorrect results at https://nmap.org/submit/ .
Nmap done: 1 IP address (1 host up) scanned in 0.94 seconds

Vulnerability description

We found that the SSH service with username/password authentication is publicly accessible. Network administrators often use remote administration protocols to control devices like switches, routers, and other essential systems. However, allowing these services to be accessible via the Internet can increase security risks, creating potential opportunities for attacks on the organization.

Risk description

Exposing this service online with username/password authentication can enable attackers to launch authentication attacks, like guessing login credentials, and potentially gaining unauthorized access. Vulnerabilities, such as unpatched software, protocol flaws, or backdoors could also be exploited. An example is the CVE-2024-3094 (XZ Utils Backdoor) vulnerability.

Recommendation

We recommend turning off SSH with username/password authentication access over the Internet and instead using a Virtual Private Network (VPN) that mandates two-factor authentication (2FA). If the SSH service is essential for business purposes, we recommend limiting access only from designated IP addresses using a firewall. Furthermore, it is advisable to utilize SSH Public Key Authentication since it employs a key pair to verify the identity of a user or process.

Evidence

We managed to detect a publicly accessible MySQL service.

PORT STATE SERVICE VERSION
3306/tcp open mysql MySQL 5.5.5-10.3.34-MariaDB-0ubuntu0.20.04.1

Vulnerability description

We identified that the MySQL service is publicly accessible. MySQL serves as a common database for numerous web applications and services for data storage, 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 MySQL service. Furthermore, they could exploit zero-day vulnerabilities to obtain remote access to the MySQL database server, thereby gaining complete control over its operating system and associated services. Such an attack could lead to the exposure of confidential or sensitive information.

Recommendation

We recommend turning off public Internet access to MySQL and opting for a Virtual Private Network (VPN) that enforces two-factor authentication (2FA). Avoid enabling direct user authentication to the MySQL service via the Internet, as this could enable attackers to engage in password-guessing and potentially initiate attacks leading to complete control. However, if the MySQL service is required to be directly accessible over the Internet, we recommend reconfiguring it to be accessible only from known IP addresses.

Evidence

Risk level	CVSS	CVE	Summary
	6.2	CVE-2022-4900	A vulnerability was found in PHP where setting the environment variable PHP_CLI_SERVER_WORKERS to a large value leads to a heap buffer overflow.
	5.3	CVE-2024-5458	In PHP versions 8.1.* before 8.1.29, 8.2.* before 8.2.20, 8.3.* before 8.3.8, due to a code logic error, filtering functions such as filter_var when validating URLs (FILTER_VALIDATE_URL) for certain types of URLs the function will result in invalid user information (username + password part of URLs) being treated as valid user information. This may lead to the downstream code accepting invalid URLs as valid and parsing them incorrectly.

Vulnerability description

Vulnerabilities found for PHP 7.4.33

Risk description

These vulnerabilities expose the affected applications to the risk of unauthorized access to confidential data and possibly to denial of service attacks. An attacker could search for an appropriate exploit (or create one) for any of these vulnerabilities and use it to attack the system. Notes: - The vulnerabilities are identified based on the server's version.; - Only the first 5 vulnerabilities with the highest risk are shown for each port.;

Recommendation

We recommend you to upgrade the affected software to the latest version in order to eliminate the risks imposed by these vulnerabilities.

Evidence

We managed to detect a publicly accessible File Transfer Protocol (FTP) service.

PORT STATE SERVICE VERSION
21/tcp open ftp ProFTPD

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 Post Office Protocol (POP3) service.

Starting Nmap ( https://nmap.org ) at 2025-04-17 08:44 EEST
Nmap scan report for www.proteinbank.it (138.201.139.240)
Host is up (0.020s latency).
rDNS record for 138.201.139.240: static.240.139.201.138.clients.your-server.de

PORT    STATE SERVICE  VERSION
995/tcp open  ssl/pop3 Dovecot pop3d
|_pop3-capabilities: PIPELINING SASL(PLAIN LOGIN DIGEST-MD5 CRAM-MD5) APOP TOP UIDL CAPA RESP-CODES AUTH-RESP-CODE USER
Service Info: Host: h1.proteinitalia.com

Service detection performed. Please report any incorrect results at https://nmap.org/submit/ .
Nmap done: 1 IP address (1 host up) scanned in 6.70 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

We managed to detect that MySQL has reached the End-of-Life (EOL).

Version detected: 5.5.5-10.3.34-mariadb-0ubuntu0.20.04.1 End-of-life date: 2020-04-11 Latest version for the cycle: 5.5.68 This release cycle (5.5) does have long-term-support (LTS). The cycle was released on 2012-04-11 and its latest release date was 2020-05-06.

Risk description

Using end-of-life (EOL) software poses significant security risks for organizations. EOL software no longer receives updates, including critical security patches. This creates a vulnerability landscape where known and potentially new security flaws remain unaddressed, making the software an attractive target for malicious actors. Attackers can exploit these vulnerabilities to gain unauthorized access, disrupt services, or steal sensitive data. Moreover, without updates, compatibility issues arise with newer technologies, leading to operational inefficiencies and increased potential for system failures. Additionally, regulatory and compliance risks accompany the use of EOL software. Many industries have strict data protection regulations that require up-to-date software to ensure the highest security standards. Non-compliance can result in hefty fines and legal consequences. Organizations also risk damaging their reputation if a breach occurs due to outdated software, eroding customer trust and potentially leading to a loss of business. Therefore, continuing to use EOL software undermines both security posture and business integrity, necessitating timely upgrades and proactive risk management strategies.

Recommendation

To mitigate the risks associated with end-of-life (EOL) software, it's crucial to take proactive steps. Start by identifying any EOL software currently in use within your organization. Once identified, prioritize upgrading or replacing these applications with supported versions that receive regular updates and security patches. This not only helps close security gaps but also ensures better compatibility with newer technologies, enhancing overall system efficiency and reliability.Additionally, develop a comprehensive software lifecycle management plan. This plan should include regular audits to identify upcoming EOL dates and a schedule for timely updates or replacements. Train your IT staff and users about the importance of keeping software up to date and the risks associated with using outdated versions. By maintaining a proactive approach to software management, you can significantly reduce security risks, ensure compliance with industry regulations, and protect your organization's reputation and customer trust.

Evidence

We managed to detect that PHP has reached the End-of-Life (EOL).

Version detected: 7.4.33 End-of-life date: 2022-11-28 Latest version for the cycle: 7.4.33 This release cycle (7.4) doesn't have long-term-support (LTS). The cycle was released on 2019-11-28 and its latest release date was 2022-11-03. The support ended on 2021-11-28.

Risk description

Recommendation

Evidence

Domain Queried	DNS Record Type	Description	Value
www.proteinbank.it	A	IPv4 address	138.201.139.240

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.

Operating System
Linux 5.0 - 5.4

Evidence

Software / Version	Category
WordPress 6.7.2	CMS, Blogs
MySQL	Databases
PHP 7.4.33	Programming languages
Bootstrap	UI frameworks
Contact Form 7 6.0.6	WordPress plugins, Form builders
Nginx	Web servers, Reverse proxies
RankMath SEO	WordPress plugins, SEO
Envo eCommerce 1.2.1	WordPress themes
WooCommerce 9.8.1	Ecommerce, WordPress plugins
Yandex.Metrika	Analytics
WhatsApp Business Chat	Live chat
Magnific Popup 1.0	JavaScript libraries
jsDelivr	CDN
jQuery Migrate 3.4.1	JavaScript libraries
jQuery	JavaScript libraries

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
Plesk	Hosting panels
Sentry	Issue trackers
Nginx	Web servers, Reverse proxies
RequireJS	JavaScript frameworks
Prototype	JavaScript frameworks
React Router 6	JavaScript frameworks
React	JavaScript frameworks
core-js 3.38.1	JavaScript libraries
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.