Search for packages
| purl | pkg:maven/org.bouncycastle/bcprov-jdk15on@1.48 |
| Next non-vulnerable version | None. |
| Latest non-vulnerable version | None. |
| Risk | 4.5 |
| Vulnerability | Summary | Fixed by |
|---|---|---|
|
VCID-2u2e-ux7t-aaar
Aliases: CVE-2020-15522 GHSA-6xx3-rg99-gc3p |
Timing based private key exposure in Bouncy Castle |
Affected by 6 other vulnerabilities. |
|
VCID-8kgr-r3r4-aaak
Aliases: CVE-2024-30171 GHSA-v435-xc8x-wvr9 |
An issue was discovered in Bouncy Castle Java TLS API and JSSE Provider before 1.78. Timing-based leakage may occur in RSA based handshakes because of exception processing. |
Affected by 0 other vulnerabilities. |
|
VCID-99hh-6w2u-aaaa
Aliases: CVE-2024-30172 GHSA-m44j-cfrm-g8qc |
An issue was discovered in Bouncy Castle Java Cryptography APIs before 1.78. An Ed25519 verification code infinite loop can occur via a crafted signature and public key. |
Affected by 0 other vulnerabilities. |
|
VCID-a8mw-s4pr-aaab
Aliases: CVE-2018-5382 GHSA-8477-3v39-ggpm |
The default BKS keystore use an HMAC that is only 16 bits long, which can allow an attacker to compromise the integrity of a BKS keystore. Bouncy Castle release 1.47 changes the BKS format to a format which uses a 160 bit HMAC instead. This applies to any BKS keystore generated prior to BC 1.47. For situations where people need to create the files for legacy reasons a specific keystore type "BKS-V1" was introduced in 1.49. It should be noted that the use of "BKS-V1" is discouraged by the library authors and should only be used where it is otherwise safe to do so, as in where the use of a 16 bit checksum for the file integrity check is not going to cause a security issue in itself. |
Affected by 7 other vulnerabilities. |
|
VCID-p1ac-tc9q-aaaa
Aliases: CVE-2024-29857 GHSA-8xfc-gm6g-vgpv |
An issue was discovered in ECCurve.java and ECCurve.cs in Bouncy Castle Java (BC Java) before 1.78, BC Java LTS before 2.73.6, BC-FJA before 1.0.2.5, and BC C# .Net before 2.3.1. Importing an EC certificate with crafted F2m parameters can lead to excessive CPU consumption during the evaluation of the curve parameters. |
Affected by 0 other vulnerabilities. |
|
VCID-tt54-7vmn-aaaj
Aliases: CVE-2023-33202 GHSA-wjxj-5m7g-mg7q |
Bouncy Castle for Java before 1.73 contains a potential Denial of Service (DoS) issue within the Bouncy Castle org.bouncycastle.openssl.PEMParser class. This class parses OpenSSL PEM encoded streams containing X.509 certificates, PKCS8 encoded keys, and PKCS7 objects. Parsing a file that has crafted ASN.1 data through the PEMParser causes an OutOfMemoryError, which can enable a denial of service attack. (For users of the FIPS Java API: BC-FJA 1.0.2.3 and earlier are affected; BC-FJA 1.0.2.4 is fixed.) | There are no reported fixed by versions. |
|
VCID-x6rq-m1e2-aaab
Aliases: CVE-2020-26939 GHSA-72m5-fvvv-55m6 |
Observable Differences in Behavior to Error Inputs in Bouncy Castle |
Affected by 6 other vulnerabilities. |
| Vulnerability | Summary | Aliases |
|---|---|---|
| VCID-6w5e-vydq-aaac | The TLS implementation in the Bouncy Castle Java library before 1.48 and C# library before 1.8 does not properly consider timing side-channel attacks on a noncompliant MAC check operation during the processing of malformed CBC padding, which allows remote attackers to conduct distinguishing attacks and plaintext-recovery attacks via statistical analysis of timing data for crafted packets, a related issue to CVE-2013-0169. |
CVE-2013-1624
GHSA-8353-fgcr-xfhx |