Server Software Version Disclosure

HTTP response headers or default pages name the web server, framework or language and their versions, which helps an attacker select known exploits.

SeverityInformational
CVSS 3.10 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N Open in the calculator
CVSS 4.00 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:N/SA:N Open in the calculator
CWECWE-497: Exposure of Sensitive System Information to an Unauthorized Control Sphere
OWASP Top 10A01:2025 Broken Access Control
MITRE ATT&CKT1592.002 Software
CategoryInformation Disclosure

Description

The server identifies the software that handles requests, and often its exact version, in HTTP response headers and default content. Common sources are the Server header, for example naming Apache httpd, nginx or IIS with a version number and operating system; X-Powered-By, for example naming PHP or ASP.NET; X-AspNet-Version and X-AspNetMvc-Version; generator meta tags added by content management systems; and the signature line on default error pages.

The disclosure has no direct impact, but it saves an attacker some reconnaissance effort: a precise version can be compared with published vulnerabilities, and automated tools can target the server with exploits for the identified version, so it matters more if the software is not kept up to date. A version is not proof that the software is vulnerable, however: operating system vendors often backport security fixes without changing the version string, so a version that appears outdated should be confirmed against the vendor's patch information before a missing patch is reported. Where the disclosed version is confirmed to be outdated or unsupported, that should be reported as a separate finding.

The information is collected passively from ordinary responses and is reported by almost every scanner. Removing the banner is a hardening measure that reduces the information freely available, not a substitute for patching, and it does not prevent fingerprinting, as software can usually be identified from its behaviour, default pages and response formats.

Remediation

Remove or minimise identifying headers and banners on every server and proxy in the request path:

  • nginx: set server_tokens off; to remove the version from the Server header and error pages, and use proxy_hide_header or fastcgi_hide_header to drop X-Powered-By from upstream responses.
  • Apache httpd: set ServerTokens Prod and ServerSignature Off in the main server configuration.
  • IIS and ASP.NET: remove X-Powered-By under customHeaders, set enableVersionHeader="false" on httpRuntime, set MvcHandler.DisableMvcResponseHeader = true for ASP.NET MVC and, on IIS versions that support it, set removeServerHeader="true" on requestFiltering.
  • PHP: set expose_php = Off in php.ini.
  • Remove generator meta tags and version strings from page templates, and replace default error pages with custom ones.
nginx (http block): server_tokens off; fastcgi_hide_header X-Powered-By; Apache httpd (main server configuration): ServerTokens Prod ServerSignature Off IIS (web.config): <system.web> <httpRuntime enableVersionHeader="false" /> </system.web> <system.webServer> <security> <requestFiltering removeServerHeader="true" /> </security> <httpProtocol> <customHeaders> <remove name="X-Powered-By" /> </customHeaders> </httpProtocol> </system.webServer>

The nginx and Apache settings still name the product, without its version. Confirm the change by inspecting the headers of normal pages, error pages and static files.

References


Add This Finding to Your Library

In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.

Free trial  ·  No card required

Only need the reporting? Our reporting tool is free and open source, with the same library.


More Web Applications Findings

Every Web Applications finding