Skip to content

Why a finding is or isn't shown

A release shows a finding when Affectra matched a component of one of its uploaded SBOMs to a vulnerability, the vulnerability is not withdrawn, and no VEX statement resolved it. This page states the rules, so you can tell why a finding is there, or why one is missing. The names used here are explained in How matching works.

The findings of a release come from the SBOMs uploaded to it.

A component without a version is never matched. In a purl the version follows the @. Without it, there is nothing to compare with the affected versions.

The package is in an advisory, at an affected version

Section titled “The package is in an advisory, at an affected version”

For a purl in a supported ecosystem, Affectra looks for advisories of the same ecosystem and the same package name. Names must be equal, letter for letter. For PyPI, Affectra lowers the case and turns every run of _, . and - into one - first, as PyPI does.

The version then has to be affected. An advisory says so in one of two ways:

  • It lists the version. The version must be equal to a listed one.
  • It gives a range: affected from one version, fixed in another, or affected up to a last version. The component version must be in the range.

Either is enough. A version in the range is affected even when the advisory’s list leaves it out, because such lists are often incomplete. An advisory that only lists versions never says that your version is not affected, so it never makes the sources disagree.

How versions are compared depends on the ecosystem:

Ecosystem Versions are compared
Debian, Ubuntu As the Debian package manager does, including epochs and ~.
npm, Go, crates.io As semantic versions.
Alpine Approximately, with Alpine’s rules.
PyPI As Python does (PEP 440), including epochs and pre-, post- and development releases.
Maven As Maven does, including qualifiers such as beta, RC and SNAPSHOT.
RubyGems As RubyGems does: a version with a letter, such as 1.0.0.pre, is a pre-release.
NuGet As NuGet does, including four-part versions such as 4.5.0.1.
Packagist As Composer does, including alpha, beta, RC and a leading v.

For PyPI, Maven, RubyGems, NuGet and Packagist, Affectra compares versions with the same rules as OSV. A version that does not follow the ecosystem’s version format, such as a Composer branch (dev-main), a Maven property (${revision}) or a PyPI version that isn’t PEP 440, has no place in a range. Such a component is only found by an advisory that lists its version exactly, so a vulnerability can be missing. Put the released version in the SBOM to avoid that.

Ranges of commit hashes never match a released version.

Distribution packages are matched by their release and source package

Section titled “Distribution packages are matched by their release and source package”

Debian and Ubuntu advisories name the source package and the distribution release, not the binary package. Affectra therefore needs two things in the purl:

  • the distribution release, in the distro qualifier, for example distro=debian-12 or distro=ubuntu-22.04. Without it, a Debian or Ubuntu package has no match. Alpine needs a distro with a major and a minor version, for example alpine-3.18;
  • the source package, in the upstream qualifier, for example upstream=openssl. Without it, the binary package name is used. The collector and common SBOM tools write both.

Other Debian derivatives, such as Raspbian, are not matched. A package that a distribution’s advisories describe is compared with the distribution’s fixed version, not the upstream’s. A fix that the distribution backported counts.

Distribution advisories decide, not the NVD

Section titled “Distribution advisories decide, not the NVD”

If a purl is in a supported ecosystem, only that ecosystem’s advisories are used. The NVD and vendor advisories are not asked, even when the ecosystem’s advisories have nothing on the package. A component therefore has findings from the ecosystem’s advisories or from the NVD and vendor advisories, never from both.

For a CPE match, vendor, product and version fit

Section titled “For a CPE match, vendor, product and version fit”

Components that a purl cannot describe are matched against the NVD by CPE. The CPE comes from your SBOM (for a private component), from Affectra’s short list of known packages, such as ESP-IDF, ESPHome and Mbed TLS, or from your own mapping. It matches an NVD entry when:

  • the component has a concrete version;
  • the product is equal, and the vendor is equal or the component’s vendor is a wildcard;
  • the version equals the one the entry names, or is inside the bounds the entry gives. An entry for every version, with no bounds, never matches.

For an NVD entry with a platform, your SBOM doesn’t name another one

Section titled “For an NVD entry with a platform, your SBOM doesn’t name another one”

Some NVD entries are affected only on a platform: Flash Player when run on macOS, Linux or Windows, or this firmware on this router. Affectra looks for the platform in the SBOMs that contain the component:

  • The SBOM contains the platform, by its CPE. The finding is shown.
  • The SBOM names no platform of that kind. The finding is shown. Most SBOMs list neither the operating system nor the device, so Affectra can’t rule it out. If the platform doesn’t apply to you, record that with a VEX statement.
  • The SBOM names another operating system or another device, by a CPE of an operating system (o) or a device (h), and none of the ones the entry lists. There is no finding: a product runs one operating system on one device. Other components, such as applications, never rule a platform out.

A finding is shown when this holds in at least one SBOM of your organization that contains the component. A component that other organizations use too, and that Affectra matches through its short list of known packages, is matched without looking at your SBOM: its findings can’t depend on one organization’s upload. Then the finding is shown, as when the SBOM names no platform. Your package mappings look at your own SBOMs only.

CPE matching needs the NVD data. Without it, these components are not checked against the NVD, and the release says so.

For a vendor advisory, the product is known affected at your version

Section titled “For a vendor advisory, the product is known affected at your version”

A vendor advisory creates a finding for a component that a purl in a supported ecosystem cannot describe when it names the component by purl, or by a CPE that fits as above, and says the product is known affected at the component’s version: that version, or inside a vers: range. A fixed version at or below yours in the same advisory means no finding. An advisory that says “all versions”, or gives its range only in words, never creates a finding by itself.

A release shows one row for each CVE, however many advisories report it and however many components they match. The row lists every advisory behind it in its source strip: the vendor’s own advisory, a coordinator’s, OSV and the NVD, in that order of authority. The best-ranked one supplies the title when the NVD isn’t among them, and the timeline you see first. An advisory without a CVE is a row of its own, unless it is an alias of another advisory without a CVE: then the two share a row, under the smaller ID. Each advisory picks the smallest ID among its own and the aliases it names, so the advisory with the larger ID must name the other one (Go and Python advisories name the GitHub advisory). Only aliases that Affectra has an advisory for count, and aliases don’t chain: if A names B and B names C, A and C don’t share a row through B. An advisory with two CVEs is in two rows. See One finding for several advisories.

An advisory can name a component of your release and say that its version is not affected. Then it is no match. If another advisory for the same CVE matches that component, the row shows Sources disagree, a hollow dot (○) for the advisory that excludes, and a marked line in the table under Details. It is information for you, never a reason to hide the finding: a statement on the CVE resolves it.

A mapping applies when the package has no purl match

Section titled “A mapping applies when the package has no purl match”

Your package mapping names a package without its version. It is applied to components with exactly that package, so pkg:github/acme/lib does not apply to pkg:github/acme/lib-extra. The component also needs a version, and a purl that no supported ecosystem describes. Findings from a mapping are marked your mapping, and only your releases have them.

Advisories and CVEs that their source withdrew or rejected are not shown. When the source withdraws an advisory, the next load removes the finding.

A finding whose current status is Not affected or Fixed is resolved. The release list hides it, and shows it under All. A statement on the CVE resolves the whole row, whatever its sources say. Affected and Under investigation leave it open. Assess findings with VEX explains how statements on an advisory and on its CVEs combine.

Your SBOM names an operating system or a device, and the NVD entry is affected only on others. See For an NVD entry with a platform.

When a component is updated, or an advisory changes its ranges, the next match removes the finding.

Why you may not see a finding you expected

Section titled “Why you may not see a finding you expected”

Check these in order:

  1. Matching is not finished. The line above the list says Matching in progress while components wait.
  2. A source is stale or was never loaded. The line above the list warns you. See Vulnerability sources.
  3. The component is not checkable. The line says how many components were checkable. A component without a version, or with a purl of an unsupported type such as generic and no CPE, cannot be matched. Add a version, add a CPE to the SBOM, or add a package mapping.
  4. A Debian or Ubuntu package lacks distro. See above.
  5. The NVD is unavailable. The release says NVD sync is off; CPE matches and CVSS scores are missing until it is back.
  6. The finding is resolved. Select All.
  7. The ecosystem lists versions only. See the table above.
  8. The feed is off for your organization. An admin turned NVD or a CSAF provider off in Settings, so its findings are hidden. See Choose vulnerability feeds.
  9. Another advisory is on the same row. One row covers every advisory for its CVE. Look at the source strip, or search for the advisory’s ID: the row that has it stays, and its chip is highlighted.

Why you may see a finding you did not expect

Section titled “Why you may see a finding you did not expect”

Select Details on the row. Why it’s here says whether it was found at your upload, came with a new or updated advisory, or came through your mapping. The component tag shows how it was matched: no mark for a package URL, CPE (the NVD or a vendor advisory), or your mapping. A finding can also be correct although it does not apply to your build. That is what a VEX statement is for.

An NVD finding can depend on a platform your SBOM doesn’t name, such as an operating system. Add the operating system’s or the device’s CPE to the SBOM: entries for other platforms go when Affectra next matches the component, at the latest after the next load of advisory data.