CVE Management

CVE (Common Vulnerabilities and Exposures) management is the ongoing process of identifying, assessing, remediating and monitoring known security vulnerabilities in IT systems. It forms the backbone of modern vulnerability management, helping to protect systems from cyber attacks and to meet regulatory requirements such as the EU Cyber Resilience Act.

The CVE management lifecycle has four key stages:

1. Identification

Inventory of all software components in use (the SBOM — see Software Bill of Materials (SBOM)) and comparison with the publicly accessible CVE databases.

2. Assessment

Determining the relevance of a vulnerability to your own system, usually via the standardised CVSS (Common Vulnerability Scoring System), which rates severity from 0.0 to 10.0.

3. Prioritisation & Resolution (Patch Management)

Risk-based fixing of the most critical vulnerabilities first, e.g. by installing security updates.

4. Reporting & Documentation

Documenting all actions and continuously monitoring the system software to minimise vulnerabilities in the long term and ensure compliance.

Vulnerability checking with Yocto

Yocto offers two classes for this — cve-check (traditional) and vex (modern, CRA-oriented). They are mutually exclusive.

Class

How it works

Limitations

cve-check

Compares the names and versions of the built packages against the CVE databases stored in Yocto; generates JSON reports listing which CVEs may apply.

Heavily dependent on the original build directory; relies on the (often incomplete) CPE information in the databases.

vex

Generates structured VEX documents in OpenVEX format — states not only whether a package is vulnerable, but whether it is exploitable in the specific configuration of your system. Works on the SPDX SBOM, so scans can run independently of the original BitBake build.

Introduced with Yocto 6.0 (wrynose), backported to Scarthgap (since point release 5.0.15).

To enable either class, add it to conf/local.conf:

INHERIT += "cve-check"    # or: INHERIT += "vex"

Note

The Ka-Ro distros (karo-minimal, karo-wayland, …) already enable the modern variant: INHERIT += "vex" together with create-spdx-3.0 and SPDX_INCLUDE_VEX = "current" (see Software Bill of Materials (SBOM)), so VEX data is embedded in the generated SBOM by default — no local.conf change needed.

Please also see the Yocto documentation on vulnerability checking at build time.

Scanning with VulnScout (open source)

Instead of commercial tools, you can use VulnScout: it analyses software components and dependencies based on the SBOM and the CVE/VEX data generated during the build. Supported input formats: CycloneDX, SPDX, Yocto JSON files, OpenVEX.

Installation — clone the layer into your BSP’s layers directory (sources for the NXP BSP, layers for the Mainline BSP):

cd <path-to-your-BSP-installation>/<layers-dir>
git clone -b scarthgap https://github.com/savoirfairelinux/meta-vulnscout.git

Add it to your build:

BBLAYERS += "${BSPDIR}/<layers-dir>/meta-vulnscout"

Configuration — in conf/local.conf:

# Required settings for VulnScout
require conf/distro/include/vulnscout-core.inc

Run the scan for an image, then open the results in your browser:

bitbake karo-image-weston -c vulnscout
# then open http://localhost:7275