Service Version Disclosure

Network services reveal their software name and version in banners or responses, which helps an attacker select exploits for known vulnerabilities.

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

Many network services identify themselves when a client connects or in their responses. SSH, FTP, SMTP, POP3 and IMAP servers send a greeting banner, DNS servers may answer queries for their version, SNMP agents report a system description, and management interfaces often show versions on their login pages. These frequently include the product name and exact version, and sometimes the operating system and its patch level.

The disclosure lets an attacker match each service against public vulnerability databases and exploit collections without probing it further, focus effort on hosts that run outdated software, and choose a specific exploit rather than trying many. This reduces the effort needed to find exploitable weaknesses and makes attacks quicker and quieter, and its significance rises where the disclosed version is out of date, since an attacker can then go straight to a known exploit. It is not a vulnerability in itself and has no direct effect on the confidentiality, integrity or availability of the host or its data: where the disclosed version is affected by known vulnerabilities, those are reported separately as outdated software, and version details in web server headers are covered by a separate web application finding.

It is identified by banner grabbing and service fingerprinting, for example with Nmap version detection (-sV) or by connecting with a client such as netcat. Removing a banner does not prevent fingerprinting by behaviour, so this is a hardening measure rather than a control that stops identification.

Remediation

  • Configure each service to send a generic greeting without product and version details, where the software allows it: for example smtpd_banner in Postfix, smtp_banner in Exim, the receive connector Banner parameter in Microsoft Exchange, ftpd_banner in vsftpd, ServerIdent in ProFTPD, and the version option in BIND, which controls the answer to version.bind queries.
  • For OpenSSH, the protocol version string includes the software version and cannot be removed without rebuilding the software; on Debian and Ubuntu, DebianBanner no in sshd_config removes the additional distribution and patch-level suffix.
  • Remove version details from SNMP system descriptions, login pages and management interfaces where the product allows it.
  • Above all, keep the disclosed software up to date, since an accurate banner on a fully patched service gives an attacker little to use, and treat banner changes as hardening rather than protection.
# Postfix (main.cf) smtpd_banner = $myhostname ESMTP # vsftpd (vsftpd.conf) ftpd_banner=FTP service ready # ProFTPD (proftpd.conf) ServerIdent on "FTP service ready" # BIND (named.conf, options block) version "not disclosed";

Confirm the fix by repeating the banner grab and version scan and checking that version numbers are no longer returned.

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 Network Services Findings

Every Network Services finding