Bug 14495 - Implement CVE checking on all packages in a SBOM/manifest
Summary: Implement CVE checking on all packages in a SBOM/manifest
Status: RESOLVED WORKSFORME
Alias: None
Product: Security - Recipe Upgrade
Classification: Build System, Metadata & Runtime
Component: security (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium+ enhancement
Target Milestone: 4.1 M1
Assignee: Ross Burton
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2021-08-02 15:49 UTC by Michael Opdenacker
Modified: 2022-04-28 15:05 UTC (History)
2 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Yes (doc changes required)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Opdenacker 2021-08-02 15:49:17 UTC
This was initially proposed by Richard Purdie on
https://bugzilla.yoctoproject.org/show_bug.cgi?id=14419

The question was:
"How to check for vulnerabilities in my image without regenerating it, and without runing "bitbake -c cve_check" on individual package names?"

His answer was:

"Ultimately we will generate an SBOM/manifest with the image and it would be good if we could run a new check of that manifest against the CVEs. That isn't currently implemented but should be and should perhaps be a new bug?"

Such a check would definitely be useful for production project maintainers, and will for sure be recommended in our manuals.
Comment 1 Ross Burton 2022-04-28 15:05:01 UTC
"bitbake core-image-minimal --runall cve_check" will do that.