Skip to content

org.bouncycastle:bc-fips (Maven)

Advisories
5
Latest version
—
License
—
OpenSSF Scorecard
—

How to fix

Upgrading to 2.0.1 or later clears every advisory below that has a fix.

Upgrade commands
maven
<dependency><groupId>org.bouncycastle</groupId><artifactId>bc-fips</artifactId><version>2.0.1</version></dependency>
gradle
implementation("org.bouncycastle:bc-fips:2.0.1")

Known vulnerabilities

AdvisorySeverityAffectedFixed in
GHSA-67mf-3cr5-8w23
Bouncy Castle for Java on All (API modules) allows Excessive Allocation
Medium
EPSS 0.54%
>= 1.0.0, < 1.0.2.6
1.0.2.6
GHSA-67mf-3cr5-8w23
Bouncy Castle for Java on All (API modules) allows Excessive Allocation
Medium
EPSS 0.54%
>= 2.0.0, < 2.0.1
2.0.1
GHSA-8xfc-gm6g-vgpv
Bouncy Castle certificate parsing issues cause high CPU usage during parameter evaluation.
High
EPSS 1.10%
< 1.0.2.5
1.0.2.5
GHSA-6xx3-rg99-gc3p
Timing based private key exposure in Bouncy Castle
Medium
EPSS 1.52%
< 1.0.2.1
1.0.2.1
GHSA-72m5-fvvv-55m6
Observable Differences in Behavior to Error Inputs in Bouncy Castle
Medium
EPSS 0.92%
< 1.0.2
1.0.2
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor