org.bouncycastle:bcprov-jdk15on vulnerabilities
The Bouncy Castle Crypto package is a Java implementation of cryptographic algorithms. This jar contains JCE provider and lightweight API for the Bouncy Castle Cryptography APIs for JDK 1.5 and up.
- Registry
- Maven
- Latest
- 1.70
- License
- Bouncy Castle Licence
25 known advisories
The latest version, 1.70, is affected by 5 of them.
Is your project on an affected org.bouncycastle:bcprov-jdk15on?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for org.bouncycastle:bcprov-jdk15on
Bouncy Castle for Java GOST 28147 CTR mode reuses keystream after 255 blocks
- Affected
- <=1.7.0
- Fixed in
- No fix released
Bouncy Castle certificate parsing issues cause high CPU usage during parameter evaluation.
- Affected
- <1.78
- Fixed in
- 1.78
Bouncy Castle affected by timing side-channel for RSA key exchange ("The Marvin Attack")
- Affected
- <1.78
- Fixed in
- 1.78
Bouncy Castle Java Cryptography API vulnerable to DNS poisoning
- Affected
- >=1.61 <1.78
- Fixed in
- 1.78
Bouncy Castle Denial of Service (DoS)
- Affected
- All versions
- Fixed in
- No fix released
Bouncy Castle For Java LDAP injection vulnerability
- Affected
- >=1.49 <=1.70
- Fixed in
- No fix released
Improper Input Validation in Bouncy Castle
- Affected
- <1.48
- Fixed in
- 1.48
Observable Discrepancy in BouncyCastle
- Affected
- <1.0.3
- Fixed in
- 1.0.3
Improper Validation of Integrity Check Value in Bouncy Castle
- Affected
- <1.50
- Fixed in
- 1.50
Timing based private key exposure in Bouncy Castle
- Affected
- <1.66
- Fixed in
- 1.66
Logic error in Legion of the Bouncy Castle BC Java
- Affected
- >=1.65 <1.67
- Fixed in
- 1.67
Observable Differences in Behavior to Error Inputs in Bouncy Castle
- Affected
- <1.61
- Fixed in
- 1.61
Moderate severity vulnerability that affects org.bouncycastle:bcprov-jdk14 and org.bouncycastle:bcprov-jdk15
- Affected
- <1.56
- Fixed in
- 1.56
In Bouncy Castle JCE Provider the DHIES implementation allowed the use of ECB mode
- Affected
- <1.56
- Fixed in
- 1.56
Moderate severity vulnerability that affects org.bouncycastle:bcprov-jdk14 and org.bouncycastle:bcprov-jdk15
- Affected
- <1.51
- Fixed in
- 1.51
In Bouncy Castle JCE Provider the ECIES implementation allowed the use of ECB mode
- Affected
- <1.56
- Fixed in
- 1.56
In Bouncy Castle JCE Provider the other party DH public key is not fully validated
- Affected
- <1.56
- Fixed in
- 1.56
In Bouncy Castle JCE Provider the DSA key pair generator generates a weak private key if used with default values
- Affected
- <1.56
- Fixed in
- 1.56
In Bouncy Castle JCE Provider ECDSA does not fully validate ASN.1 encoding of signature on verification
- Affected
- <1.56
- Fixed in
- 1.56
Moderate severity vulnerability that affects org.bouncycastle:bcprov-jdk14 and org.bouncycastle:bcprov-jdk15
- Affected
- <1.56
- Fixed in
- 1.56
The Bouncy Castle JCE Provider carry a propagation bug
- Affected
- >=1.51 <1.56
- Fixed in
- 1.56
Moderate severity vulnerability that affects org.bouncycastle:bcprov-jdk14 and org.bouncycastle:bcprov-jdk15
- Affected
- <1.56
- Fixed in
- 1.56
In Bouncy Castle JCE Provider it is possible to inject extra elements in the sequence making up the signature and still have it validate
- Affected
- >=1.38 <1.56
- Fixed in
- 1.56
Deserialization of Untrusted Data in Bouncy castle
- Affected
- >=1.57 <1.60
- Fixed in
- 1.60
Bouncy Castle has a flaw in the Low-level interface to RSA key pair generator
- Affected
- <1.60
- Fixed in
- 1.60
Is your org.bouncycastle:bcprov-jdk15on version vulnerable?
- org.bouncycastle:bcprov-jdk15on 1.705 advisories in 1.70.0
- org.bouncycastle:bcprov-jdk15on 1.695 advisories in 1.69.0
- org.bouncycastle:bcprov-jdk15on 1.685 advisories in 1.68.0
- org.bouncycastle:bcprov-jdk15on 1.675 advisories in 1.67.0
- org.bouncycastle:bcprov-jdk15on 1.666 advisories in 1.66.0
- org.bouncycastle:bcprov-jdk15on 1.657 advisories in 1.65.1
Which of your client projects still run an old org.bouncycastle:bcprov-jdk15on?
NPMscan reads the pom.xml, build.gradle and gradle.lockfile in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other Maven packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Maven registry.