org.bouncycastle:bcprov-jdk15on (Maven)
Advisories
25
Latest version
—
License
—
OpenSSF Scorecard
—
How to fix
Upgrading to 1.78 or later clears every advisory below that has a fix.
Upgrade commands
maven
<dependency><groupId>org.bouncycastle</groupId><artifactId>bcprov-jdk15on</artifactId><version>1.78</version></dependency>gradle
implementation("org.bouncycastle:bcprov-jdk15on:1.78")Known vulnerabilities
| Advisory | Severity | Affected | Fixed in |
|---|---|---|---|
| GHSA-574f-3g2m-x479 Bouncy Castle for Java GOST 28147 CTR mode reuses keystream after 255 blocks |
High EPSS 0.32% |
<= 1.7.0 | No fix yet |
| 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% |
all versions | No fix yet |
| GHSA-hr8g-6v94-x4m9 Bouncy Castle For Java LDAP injection vulnerability |
Medium EPSS 0.77% |
>= 1.49, <= 1.70 | No fix yet |
| GHSA-8353-fgcr-xfhx Improper Input Validation in Bouncy Castle |
Medium EPSS 2.97% |
< 1.48 | 1.48 |
| GHSA-wrwf-pmmj-w989 Observable Discrepancy in BouncyCastle |
Medium EPSS 24.28% |
< 1.0.3 | 1.0.3 |
| GHSA-8477-3v39-ggpm Improper Validation of Integrity Check Value in Bouncy Castle |
Medium EPSS 0.26% |
< 1.50 | 1.50 |
| GHSA-6xx3-rg99-gc3p Timing based private key exposure in Bouncy Castle |
Medium EPSS 1.52% |
< 1.66 | 1.66 |
| GHSA-73xv-w5gp-frxh Logic error in Legion of the Bouncy Castle BC Java |
High EPSS 7.22% |
>= 1.65, < 1.67 | 1.67 |
| GHSA-72m5-fvvv-55m6 Observable Differences in Behavior to Error Inputs in Bouncy Castle |
Medium EPSS 0.92% |
< 1.61 | 1.61 |
| GHSA-9gp4-qrff-c648 Moderate severity vulnerability that affects org.bouncycastle:bcprov-jdk14 and org.bouncycastle:bcprov-jdk15 |
Medium EPSS 2.56% |
< 1.56 | 1.56 |
| GHSA-2j2x-hx4g-2gf4 In Bouncy Castle JCE Provider the DHIES implementation allowed the use of ECB mode |
High EPSS 2.17% |
< 1.56 | 1.56 |
| GHSA-4mv7-cq75-3qjm Moderate severity vulnerability that affects org.bouncycastle:bcprov-jdk14 and org.bouncycastle:bcprov-jdk15 |
Medium EPSS 4.69% |
< 1.51 | 1.51 |
| GHSA-w285-wf9q-5w69 In Bouncy Castle JCE Provider the ECIES implementation allowed the use of ECB mode |
High EPSS 2.17% |
< 1.56 | 1.56 |
| GHSA-fjqm-246c-mwqg In Bouncy Castle JCE Provider the other party DH public key is not fully validated |
Low EPSS 2.17% |
< 1.56 | 1.56 |
| GHSA-rrvx-pwf8-p59p In Bouncy Castle JCE Provider the DSA key pair generator generates a weak private key if used with default values |
High EPSS 3.25% |
< 1.56 | 1.56 |
| GHSA-qcj7-g2j5-g7r3 In Bouncy Castle JCE Provider ECDSA does not fully validate ASN.1 encoding of signature on verification |
High EPSS 1.83% |
< 1.56 | 1.56 |
| GHSA-r9ch-m4fh-fc7q Moderate severity vulnerability that affects org.bouncycastle:bcprov-jdk14 and org.bouncycastle:bcprov-jdk15 |
Medium EPSS 2.56% |
< 1.56 | 1.56 |
| GHSA-r97x-3g8f-gx3m The Bouncy Castle JCE Provider carry a propagation bug |
High EPSS 2.30% |
>= 1.51, < 1.56 | 1.56 |
| GHSA-c8xf-m4ff-jcxj Moderate severity vulnerability that affects org.bouncycastle:bcprov-jdk14 and org.bouncycastle:bcprov-jdk15 |
Medium EPSS 2.71% |
< 1.56 | 1.56 |
| GHSA-4vhj-98r6-424h In Bouncy Castle JCE Provider it is possible to inject extra elements in the sequence making up the signature and still have it validate |
High EPSS 1.79% |
>= 1.38, < 1.56 | 1.56 |
| GHSA-4446-656p-f54g Deserialization of Untrusted Data in Bouncy castle |
Critical EPSS 4.77% |
>= 1.57, < 1.60 | 1.60 |
| GHSA-xqj7-j8j5-f2xr Bouncy Castle has a flaw in the Low-level interface to RSA key pair generator |
High EPSS 3.42% |
< 1.60 | 1.60 |
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