Skip to content

Drop nested wolfcrypt CPE from generated SBOMs - #27

Open
sameehj wants to merge 2 commits into
masterfrom
fix/sbom-drop-nested-wolfcrypt-cpe
Open

Drop nested wolfcrypt CPE from generated SBOMs#27
sameehj wants to merge 2 commits into
masterfrom
fix/sbom-drop-nested-wolfcrypt-cpe

Conversation

@sameehj

@sameehj sameehj commented Sep 4, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Nested wolfcrypt stays a component (supplier, version, PURL #wolfcrypt). Matching rides on cpe:2.3:a:wolfssl:wolfssl:<version> only.
  • Stop emitting 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.
  • Generator version 1.9. wolfssl CPE is unchanged. The wolfcrypt dictionary entry stays registered; it is not emitted on the nest.

Test plan

  • python -m unittest tests/test_gen_sbom.py (CI selftest)
  • Nested wolfcrypt has name/version/PURL and no cpe
  • Parent wolfssl component still has cpe:2.3:a:wolfssl:wolfssl:<version>
  • Re-vendor share/ into wolfBoot after merge (wolfglass-sync)

Made with Cursor

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
sameehj force-pushed the fix/sbom-drop-nested-wolfcrypt-cpe branch from 0494835 to ea3e8df Compare September 4, 2026 14:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant