Skip to content

Fix invalid bc-java purl for bouncycastle/fips_java_api - #33

Open
fcanogab wants to merge 1 commit into
scanoss:mainfrom
fcanogab:fix/bcfips-purl-fips-java-api
Open

Fix invalid bc-java purl for bouncycastle/fips_java_api#33
fcanogab wants to merge 1 commit into
scanoss:mainfrom
fcanogab:fix/bcfips-purl-fips-java-api

Conversation

@fcanogab

Copy link
Copy Markdown

Summary

  • data/bouncycastle/fips_java_api/purls.yml listed pkg:github/bcgit/bc-java as the source purl for the FIPS Java API product.
  • The bc-java README explicitly states: "The FIPS-certified BC distribution lives in a separate source tree with separate Maven coordinates and a separate licence — it is not what this repository builds."
  • The FIPS Java source is proprietary (available only via office@bouncycastle.org), so there is no public source-repo purl to list. The correct entry is the published Maven artifact.
  • Replaced pkg:github/bcgit/bc-java with pkg:maven/org.bouncycastle/bc-fips, which is the artifact confirmed to map to cpe:2.3:a:bouncycastle:fips_java_api:* by CVE-2022-45146 and CVE-2026-13505.

Made with Cursor

pkg:github/bcgit/bc-java points at the non-FIPS source tree, which the
bc-java README explicitly states is not the FIPS distribution's source
(separate tree, separate Maven coordinates, separate licence). Replace
it with the correct Maven purl for the artifact that actually maps to
cpe:2.3:a:bouncycastle:fips_java_api:*, confirmed by CVE-2022-45146 and
CVE-2026-13505.
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