Drop nested wolfcrypt CPE from generated SBOMs - #27
Merged
Merged
Conversation
NVD files crypto CVEs against wolfssl, not wolfcrypt. Keep the nested component (name, version, PURL) so provenance stays; matching rides on the wolfssl CPE to avoid a future double-match.
Matching rides on the wolfssl CPE. wolfcrypt stays a provenance component and must still carry a version and a PURL.
sameehj
force-pushed
the
fix/sbom-drop-nested-wolfcrypt-cpe
branch
from
September 4, 2026 14:25
0494835 to
ea3e8df
Compare
Contributor
|
Has "made with Cursor". strip that, repush, rest of it looks good |
Contributor
Author
This was in the PR Body only. Dropped. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
#wolfcrypt). Matching rides oncpe:2.3:a:wolfssl:wolfssl:<version>only.cpe:2.3:a:wolfssl:wolfcrypt. NVD files crypto CVEs against wolfssl (zero CVEs on the wolfcrypt product today). A second CPE on the same sources is a future double-match risk.Test plan
python -m unittest tests/test_gen_sbom.py(CI selftest)cpecpe:2.3:a:wolfssl:wolfssl:<version>share/into wolfBoot after merge (wolfglass-sync)