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

The old type plate

Imagine a car from model year 2019. Since then there have been three recalls, and your garage has done all the repairs. The type plate still says “2019”. Anyone who only reads the type plate thinks: “This car has three open defects.” That is wrong – the defects have been fixed, only the plate has stayed the same.

From outside, eam.ch only sees the type plate – the version number your server states. Whether the garage did the repairs cannot be seen from outside.

Why Linux servers work this way

Linux distributions such as Ubuntu, Debian or Red Hat ship their programs in a fixed version and keep it stable for years. When a security flaw becomes known, they only build the fix into the existing version instead of moving to a new one. This is called a backport. The advantage: updates change nothing in the behaviour, and the server keeps running stably.

The drawback: the version number stays “old”. Lists of known flaws work with these version numbers, however, and therefore report flaws that were closed long ago.

What this means for your findings

  • A finding marked “Backport possible” is a prompt to check, not proof of an open flaw.
  • eam.ch therefore rates such findings one level lower.
  • Exception: if a flaw is demonstrably already being used in attacks, the finding stays critical. Here it is always worth checking immediately.

What you can do

  1. Install updates: have the server updated with all package updates of the distribution, ideally automatically. That way all available fixes are included.
  2. Ask: your hosting provider or IT service provider can confirm within minutes whether the reported flaw has already been fixed in the installed package.
  3. Decide: if the flaw is fixed, you can mark the finding as “risk accepted” with a reason – for example “package up to date, CVE fixed according to Ubuntu”.
  4. Reveal less: if the version is not shown at all, you get fewer false alarms – and give attackers fewer clues.
In short: the version number shows which release your software is based on – not how recently it has been patched.

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.