org.bouncycastle:bcprov-jdk18on (Maven)

Advisories

Latest version

—

License

—

OpenSSF Scorecard

—

How to fix

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

Upgrade commands

maven

<dependency><groupId>org.bouncycastle</groupId><artifactId>bcprov-jdk18on</artifactId><version>1.84</version></dependency>

gradle

implementation("org.bouncycastle:bcprov-jdk18on:1.84")

Known vulnerabilities

Advisory	Severity	Affected	Fixed in
GHSA-p93r-85wp-75v3 Bouncy Castle Has Covert Timing Channel Vulnerability	High EPSS 0.90%	`>= 1.82, < 1.84`	`1.84`
GHSA-c3fc-8qff-9hwx Bouncy Castle has an LDAP injection	Medium EPSS 0.53%	`>= 1.74, < 1.84`	`1.84`
GHSA-574f-3g2m-x479 Bouncy Castle for Java GOST 28147 CTR mode reuses keystream after 255 blocks	High EPSS 0.32%	`>= 1.59, < 1.80.2`	`1.80.2`
GHSA-574f-3g2m-x479 Bouncy Castle for Java GOST 28147 CTR mode reuses keystream after 255 blocks	High EPSS 0.32%	`>= 1.81.0, < 1.81.1`	`1.81.1`
GHSA-574f-3g2m-x479 Bouncy Castle for Java GOST 28147 CTR mode reuses keystream after 255 blocks	High EPSS 0.32%	`>= 1.82, < 1.84`	`1.84`
GHSA-67mf-3cr5-8w23 Bouncy Castle for Java on All (API modules) allows Excessive Allocation	Medium EPSS 0.54%	`>= 1.0, < 1.78`	`1.78`
GHSA-m44j-cfrm-g8qc Bouncy Castle crafted signature and public key can be used to trigger an infinite loop	High EPSS 0.75%	`>= 1.73, < 1.78`	`1.78`
GHSA-v435-xc8x-wvr9 Bouncy Castle affected by timing side-channel for RSA key exchange ("The Marvin Attack")	Medium EPSS 0.90%	`< 1.78`	`1.78`
GHSA-8xfc-gm6g-vgpv Bouncy Castle certificate parsing issues cause high CPU usage during parameter evaluation.	High EPSS 1.10%	`< 1.78`	`1.78`
GHSA-4h8f-2wvx-gg5w Bouncy Castle Java Cryptography API vulnerable to DNS poisoning	High EPSS 0.77%	`>= 1.61, < 1.78`	`1.78`
GHSA-wjxj-5m7g-mg7q Bouncy Castle Denial of Service (DoS)	Medium EPSS 1.00%	`< 1.73`	`1.73`
GHSA-hr8g-6v94-x4m9 Bouncy Castle For Java LDAP injection vulnerability	Medium EPSS 0.77%	`< 1.74`	`1.74`

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