easm.chUnderstanding your external attack surface

Known vulnerabilities

When visible software has a known flaw: what CVE, CVSS, EPSS and the KEV list mean and how urgent an update is.

1 min read · in plain words and for experts

Diagram
  1. Visible version
  2. Match CVE, KEV, EPSS
  3. Exploited flaw
  4. Update first

The car recall

When a manufacturer finds a fault in a car model, it recalls it. Software is similar: known flaws that attackers can exploit receive a number (a CVE) and are described publicly. The manufacturer provides an update.

How eam.ch finds them

Many servers state on their own which software runs in which version – for example “Apache 2.4.49” or “OpenSSH 9.6”. eam.ch compares this information with the public lists of known flaws.

How urgent is it?

  • Critical: the flaw is demonstrably already being used in attacks. Act immediately.
  • High: serious flaw or high likelihood that it will soon be exploited. Update promptly.
  • Medium: update in the next maintenance window.

Software for which the manufacturer no longer provides updates is like a car without spare parts: new flaws stay open forever.

Caution with Linux servers: the version shown can be misleading because Linux distributions apply fixes without changing the version number. More under Backports.

What you can do

Install updates regularly, ideally automatically. And hide version details – this does not replace an update, but makes the search harder for attackers.

In short

  • Visible software versions are compared with public lists of known flaws.
  • Actively exploited flaws (KEV) are critical and must be fixed immediately.
  • Software without vendor support stays vulnerable for good.
  • With Linux packages the version can be misleading (backports).