LiveActive security incident?Get immediate response
CVE Record

CVE-2016-1000345: In the Bouncy Castle JCE Provider version 1.55 and earlier the DHIES/ECIES CBC mode vulnerable to padding o...

In the Bouncy Castle JCE Provider version 1.55 and earlier the DHIES/ECIES CBC mode vulnerable to padding oracle attack. For BC 1.55 and older, in an environment where timings can be easily observed, it is possible with enough observations to identify when the decryption is failing due to padding.

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

Security readout for executives and security teams

Plain-English summary

Bouncy Castle Java crypto provider 1.55 and earlier can leak clues during DHIES/ECIES CBC decryption. In environments where response timing is observable, an attacker may distinguish padding failures after many observations, creating a padding-oracle confidentiality risk.

Executive priority

Treat this as a targeted dependency remediation item, not an emergency based on the provided evidence. Prioritize systems handling sensitive encrypted data or exposing decryption services to untrusted users.

Technical view

The issue is a timing side channel in DHIES/ECIES CBC mode within Bouncy Castle JCE Provider versions 1.55 and earlier. Decryption failures caused by padding may be distinguishable from other outcomes, enabling padding-oracle analysis. The bundle does not provide CVSS, CWE, or a complete affected product list.

Likely exposure

Exposure is most likely in Java applications, appliances, or vendor products bundling Bouncy Castle JCE Provider 1.55 or earlier and using DHIES/ECIES with CBC mode on attacker-influenced ciphertext.

Exploitation context

The CVE description requires easily observable timing and enough observations. The source bundle does not show CISA KEV listing, active exploitation, public exploit use, or practical exploitability details for specific products.

Researcher notes

The public bundle identifies a padding-oracle timing condition but lacks CVSS, CWE, and detailed affected CPEs. Validation should focus on exact provider version, cipher mode usage, and whether timing observations are feasible from the attacker’s position.

Mitigation direction

  • Inventory applications and products that include Bouncy Castle JCE Provider.
  • Prioritize versions 1.55 and earlier for review or update.
  • Apply vendor security updates from relevant OS or product advisories.
  • Check upstream Bouncy Castle guidance and commit history before selecting a replacement version.
  • Reduce exposure where decryption timing is externally observable until updates are complete.

Validation and detection

  • Confirm the Bouncy Castle JCE Provider version in packaged applications and dependencies.
  • Identify code paths using DHIES or ECIES with CBC mode.
  • Check whether remote users can submit ciphertext to affected decryption paths.
  • Review Debian, Red Hat, Ubuntu, Oracle, and NetApp advisories for environment-specific applicability.
  • Retest after update to confirm affected provider versions are removed.
Prepared
Confidence
medium
Sources
9

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-1000345 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
8Source 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.