Skip to content
Noroxi
CVE-2015-7940· NVD / CVE Program· CNA mitre

The Bouncy Castle Java library before 1.51 does not validate a point is withing the elliptic curve, which makes it easier for remote attacke

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."

MediumCVSS 5.0 · v2.0—No exploit Fix available
Published
Nov 9, 2015
Updated
Jun 16, 2026
EPSS
4.8% · 92th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

21

Monitor

Low priority for now.

CVSS
20 / 40 · 5.0 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 4.8%

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Affected systems

VendorProduct
opensuseleap
opensuseopensuse
bouncycastlebouncy castle crypto package
oracleapplication testing suite
oracleenterprise manager ops center
oraclepeoplesoft enterprise peopletools
oraclevirtual desktop infrastructure

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • bouncycastle bouncy castle crypto packageup to 1.50 inclusive
  • opensuse leap42.1
  • opensuse opensuse13.1
  • opensuse opensuse13.2
  • oracle application testing suite12.5.0.1
  • oracle application testing suite12.5.0.2
  • oracle application testing suite12.5.0.3
  • oracle enterprise manager ops center12.1.4
  • oracle enterprise manager ops center12.2.2
  • oracle peoplesoft enterprise peopletools8.54
  • oracle peoplesoft enterprise peopletools8.55
  • oracle virtual desktop infrastructure3.5.2

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12bouncycastlebefore 1.51-11.51-1
Debian:6.0bouncycastlebefore 1.44+dfsg-2+deb6u11.44+dfsg-2+deb6u1
Debian:7bouncycastlebefore 1.44+dfsg-3.1+deb7u11.44+dfsg-3.1+deb7u1
Debian:8bouncycastlebefore 1.49+dfsg-3+deb8u11.49+dfsg-3+deb8u1
Mavenorg.bouncycastle:bcprov-jdk14before 1.511.51
Mavenorg.bouncycastle:bcprov-jdk15before 1.511.51
Mavenorg.bouncycastle:bcprov-jdk15onbefore 1.511.51
openSUSE:Tumbleweedbouncycastlebefore 1.54-1.21.54-1.2

Other highest-scoring records for the same primary product.

  • CVE-2016-0749The smartcard interaction in SPICE allows remote attackers to cause a denial of service (QEMU-KVM process crash) or possibly execute arbitra
    42Plan
  • CVE-2015-8863Off-by-one error in the tokenadd function in jv_parse.c in jq allows remote attackers to cause a denial of service (crash) via a long JSON-e
    41Plan
  • CVE-2019-18903wicked: Use-after-free when receiving invalid DHCP6 IA_PD option
    40Plan
  • CVE-2019-18902wicked: Use-after-free when receiving invalid DHCP6 client options
    40Plan
  • CVE-2016-4007Multiple unspecified vulnerabilities in the obs-service-extract_file package before 0.3-5.1 in openSUSE Leap 42.1 and before 0.3-3.1 in open
    40Plan
  • CVE-2016-3982Off-by-one error in the bmp_rle4_fread function in pngxrbmp.c in OptiPNG before 0.7.6 allows remote attackers to cause a denial of service (
    36Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:bouncycastle1.51-1 · Debian:12Package registry (OSV)
Maven:org.bouncycastle:bcprov-jdk141.51Package registry (OSV)
Maven:org.bouncycastle:bcprov-jdk151.51Package registry (OSV)
Maven:org.bouncycastle:bcprov-jdk15on1.51Package registry (OSV)
opensuse:bouncycastle1.54-1.2 · openSUSE:TumbleweedPackage registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • No special conditions are required; it is repeatable.

If successful

Confidentiality
P · data can be read
Integrity
none
Availability
none
Attack complexity
Low
Confidentiality impact
P
Integrity impact
None
Availability impact
None

CVSS vector

AV:N/AC:L/Au:N/C:P/I:N/A:N

nvd-primary

Root cause

The extension requests broader permissions than its function needs and sends the data it collects out for purposes beyond its stated function.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

json
{  "permissions": ["tabs", "<all_urls>"],  "background": { "service_worker": "analytics.js" }}

Fixed

json
{  "permissions": ["activeTab"],  "host_permissions": ["https://yildiz.example/*"]}

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records