easm.chUnderstanding your external attack surface

Backports: when the version number misleads

Why an “old” version on a Linux server can still be secure – and how to find out whether a reported flaw is really open on your system.

2 min read · in plain words and for experts

Diagram
  1. Version 2.4.37
  2. Flaw per CVE
  3. Distribution has fixed it
  4. Check the package

Mechanism

Distributions with long-term support (Debian stable, Ubuntu LTS, RHEL and derivatives, SUSE) freeze a package's upstream version for the lifetime of the release and backport security fixes as patches. The upstream version in the banner stays the same; only the package revision increases.

Visible identifierUpstreamPackage revision
SSH-2.0-OpenSSH_9.6p1 Ubuntu-3ubuntu13.5OpenSSH 9.6p11:9.6p1-3ubuntu13.5 (Ubuntu 24.04)
Server: Apache/2.4.62 (Debian)Apache 2.4.62not visible
X-Powered-By: PHP/8.1.2-1ubuntu2.20PHP 8.1.28.1.2-1ubuntu2.20
Server: Apache/2.4.37 (Red Hat Enterprise Linux)Apache 2.4.37not visible (RHEL 8)

The NVD maps vulnerabilities to upstream CPEs (e.g. cpe:2.3:a:openbsd:openssh:9.6:p1). A pure version match therefore systematically produces false positives for distribution packages. Conversely, false negatives are also possible if a package has not yet received a fix.

eam.ch rules

  • Detection via the identifier (Ubuntu, Debian, +deb, .el9, Red Hat, CentOS, SUSE, Alpine, AlmaLinux, Rocky, Fedora, Raspbian).
  • Findings vuln.cve_high/vuln.cve_medium one level lower; marked “Backport possible” with a note in the evidence.
  • vuln.kev stays critical: for actively exploited flaws, the risk of a package not yet installed outweighs.
  • No end-of-support check (vuln.eol) for distribution packages, because the release takes over maintenance.

Checking on the server

# Debian/Ubuntu: installed revision and fixes
dpkg -l openssh-server
apt changelog openssh-server | grep -m5 CVE-2024-6387
apt list --upgradable

# RHEL/Alma/Rocky
rpm -q openssh-server
rpm -q --changelog openssh-server | grep CVE-2024-6387
dnf updateinfo list --security

Then look up in the distribution's database from which revision the CVE is fixed:

If the installed revision is the same or newer, the CVE is fixed. Record this evidence (command output, link) as the reason for “risk accepted”.

Reducing the identifier

# OpenSSH (Debian/Ubuntu): hide the distribution suffix
DebianBanner no            # /etc/ssh/sshd_config, then: systemctl reload ssh
# Apache
ServerTokens Prod
ServerSignature Off
# nginx
server_tokens off;
# PHP
expose_php = Off

The SSH protocol version (SSH-2.0-OpenSSH_9.6p1) cannot be removed without recompiling. Hiding is security through obscurity and does not replace updates; it does, however, reduce automated hits and false alarms.

Further reading

In short

  • Linux distributions fix flaws without changing the version number (backport).
  • The external check only sees the version – “Backport possible” means: check it.
  • Compare the package on the server with the distribution's CVE database.
  • Fixed? “Risk accepted” with a reason; KEV flaws stay critical.

Check it yourself

Commands to verify on Linux or macOS. Replace ihre-domain.ch with your domain and only check your own systems.

apt changelog apache2 | grep -m5 CVE-
rpm -q --changelog httpd | grep -m5 CVE-