GHSA-4mv7-cq75-3qjm CVE-2015-7940
Moderate severity vulnerability that affects org.bouncycastle:bcprov-jdk14 and org.bouncycastle:bcprov-jdk15
- Severity
- Medium
- The publisher's own rating, not a CVSS score
- Exploit chance (EPSS)
- 4.69%
- Chance of exploitation in the next 30 days. Higher than 91.79% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
- Fix
- Available
- 3 packages have a fixed version
Description
The Bouncy Castle Java library before 1.51 does not validate a point is withing the elliptic curve, which makes it easier for remote attackers to obtain private keys via a series of crafted elliptic curve Diffie Hellman (ECDH) key exchanges, aka an "invalid curve attack."
Affected versions
Maven
| Package | Vulnerable | Fixed in |
|---|---|---|
| org.bouncycastle:bcprov-jdk14 | < 1.51 |
1.51 |
| org.bouncycastle:bcprov-jdk15 | < 1.51 |
1.51 |
| org.bouncycastle:bcprov-jdk15on | < 1.51 |
1.51 |
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
org.bouncycastle:bcprov-jdk14 Maven → 1.51
- maven
<dependency><groupId>org.bouncycastle</groupId><artifactId>bcprov-jdk14</artifactId><version>1.51</version></dependency>- gradle
implementation("org.bouncycastle:bcprov-jdk14:1.51")
org.bouncycastle:bcprov-jdk15 Maven → 1.51
- maven
<dependency><groupId>org.bouncycastle</groupId><artifactId>bcprov-jdk15</artifactId><version>1.51</version></dependency>- gradle
implementation("org.bouncycastle:bcprov-jdk15:1.51")
org.bouncycastle:bcprov-jdk15on Maven → 1.51
- maven
<dependency><groupId>org.bouncycastle</groupId><artifactId>bcprov-jdk15on</artifactId><version>1.51</version></dependency>- gradle
implementation("org.bouncycastle:bcprov-jdk15on:1.51")
Weakness
CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
How to prevent it
- Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
References
Advisories
Other links
- usn.ubuntu.com/3727-1
- oracle.com/security-alerts/cpuapr2020.html
- oracle.com/technetwork/security-advisory/cpujan2019-5072801.html
- lists.fedoraproject.org/pipermail/package-announce/2016-January/174915.html
- lists.opensuse.org/opensuse-security-announce/2015-11/msg00012.html
- rhn.redhat.com/errata/RHSA-2016-2035.html
- rhn.redhat.com/errata/RHSA-2016-2036.html
- web-in-security.blogspot.ca/2015/09/practical-invalid-curve-attacks.html
- debian.org/security/2015/dsa-3417
- openwall.com/lists/oss-security/2015/10/22/7
- openwall.com/lists/oss-security/2015/10/22/9
- oracle.com/technetwork/security-advisory/cpuapr2018-3678067.html
- oracle.com/technetwork/security-advisory/cpujan2018-3236628.html
- oracle.com/technetwork/security-advisory/cpujul2017-3236622.html
- oracle.com/technetwork/security-advisory/cpujul2018-4258247.html
- oracle.com/technetwork/security-advisory/cpuoct2016-2881722.html
- oracle.com/technetwork/security-advisory/cpuoct2017-3236626.html
- securityfocus.com/bid/79091
- securitytracker.com/id/1037036
- securitytracker.com/id/1037046
- securitytracker.com/id/1037053
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-p93r-85wp-75v3 Bouncy Castle Has Covert Timing Channel Vulnerability | High | Also affects org.bouncycastle:bcprov-jdk14 |
| GHSA-c3fc-8qff-9hwx Bouncy Castle has an LDAP injection | Medium | Also affects org.bouncycastle:bcprov-jdk14 |
| GHSA-574f-3g2m-x479 Bouncy Castle for Java GOST 28147 CTR mode reuses keystream after 255 blocks | High | Also affects org.bouncycastle:bcprov-jdk14 |
| GHSA-67mf-3cr5-8w23 Bouncy Castle for Java on All (API modules) allows Excessive Allocation | Medium | Also affects org.bouncycastle:bcprov-jdk14 |
| GHSA-m44j-cfrm-g8qc Bouncy Castle crafted signature and public key can be used to trigger an infinite loop | High | Also affects org.bouncycastle:bcprov-jdk14 |
| GHSA-v435-xc8x-wvr9 Bouncy Castle affected by timing side-channel for RSA key exchange ("The Marvin Attack") | Medium | Also affects org.bouncycastle:bcprov-jdk14 |
| GHSA-8xfc-gm6g-vgpv Bouncy Castle certificate parsing issues cause high CPU usage during parameter evaluation. | High | Also affects org.bouncycastle:bcprov-jdk14 |
| GHSA-4h8f-2wvx-gg5w Bouncy Castle Java Cryptography API vulnerable to DNS poisoning | High | Also affects org.bouncycastle:bcprov-jdk14 |
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