LiveActive security incident?Get immediate response
CVE Record

CVE-2016-1000340: In the Bouncy Castle JCE Provider versions 1.51 to 1.55, a carry propagation bug was introduced in the impl...

In the Bouncy Castle JCE Provider versions 1.51 to 1.55, a carry propagation bug was introduced in the implementation of squaring for several raw math classes have been fixed (org.bouncycastle.math.raw.Nat???). These classes are used by our custom elliptic curve implementations (org.bouncycastle.math.ec.custom.**), so there was the possibility of rare (in general usage) spurious calculations for elliptic curve scalar multiplications. Such errors would have been detected with high probability by the output validation for our scalar multipliers.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

Bouncy Castle JCE Provider 1.51 through 1.55 could rarely produce incorrect elliptic-curve cryptographic calculations because of a math carry bug. The source says output validation likely detected these errors, but cryptographic correctness issues still matter where affected Java libraries support security-sensitive operations.

Executive priority

Treat this as a targeted cryptography hygiene issue. It lacks a severity score and exploitation evidence, but affected cryptographic libraries should be removed from production because they can undermine correctness in security controls.

Technical view

The issue is a carry propagation defect in raw squaring math classes under org.bouncycastle.math.raw.Nat*. Those classes support custom elliptic-curve implementations under org.bouncycastle.math.ec.custom.*, creating rare spurious elliptic-curve scalar multiplication results. No CVSS, CWE, or detailed exploit prerequisites are provided in the bundle.

Likely exposure

Exposure is most likely in Java applications, appliances, or vendor platforms that bundle Bouncy Castle JCE Provider versions 1.51 to 1.55. Red Hat, Oracle, and NetApp references indicate downstream packaging concern, but this bundle does not identify specific affected product versions.

Exploitation context

The supplied sources do not show active exploitation, and KEV is false. The described behavior is a rare cryptographic calculation error, not a remotely reachable exploit path by itself. Practical risk depends on where affected Bouncy Castle code is used and whether validation or downstream patches are present.

Researcher notes

Evidence is strongest for affected Bouncy Castle versions and the defective math implementation. The bundle does not provide CVSS, CWE, exploitability analysis, or exact fixed release naming. Avoid asserting product impact beyond systems that actually include Bouncy Castle JCE Provider 1.51 to 1.55.

Mitigation direction

  • Inventory applications and vendor products for Bouncy Castle JCE Provider 1.51 through 1.55.
  • Apply vendor-supported updates from Bouncy Castle or downstream advisories.
  • Review Red Hat, Oracle, and NetApp guidance for packaged product impact.
  • Prioritize systems using elliptic-curve cryptography in authentication, signing, or key exchange.

Validation and detection

  • Check dependency manifests, SBOMs, and shaded JARs for affected bcprov versions.
  • Confirm runtime classpaths do not load Bouncy Castle JCE Provider 1.51 through 1.55.
  • Map installed vendor packages against referenced Red Hat, Oracle, and NetApp advisories.
  • Document whether elliptic-curve Bouncy Castle APIs are used in security-critical workflows.
Prepared
Confidence
medium
Sources
7

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2016-1000340 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
6Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.