LiveActive security incident?Get immediate response
CVE Record

CVE-2016-1000352: In the Bouncy Castle JCE Provider version 1.55 and earlier the ECIES implementation allowed the use of ECB...

In the Bouncy Castle JCE Provider version 1.55 and earlier the ECIES implementation allowed the use of ECB mode. This mode is regarded as unsafe and support for it has been removed from the provider.

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.55 and earlier allowed ECIES encryption to use ECB mode, which is considered unsafe. The public record says support for that mode was removed. Business risk depends on whether Java applications or vendor products actually used this ECIES configuration.

Executive priority

Treat this as dependency and cryptography hygiene with uncertain exploit urgency. Prioritize systems handling sensitive encrypted data, regulated workloads, or vendor products named in advisories. It does not appear to be a KEV-driven emergency based on the provided sources.

Technical view

The issue is a cryptographic design/implementation weakness in Bouncy Castle Java ECIES handling: ECB mode was accepted through version 1.55. Sources do not provide CVSS, CWE, exploit details, or proof of active exploitation. Downstream vendor advisories indicate affected dependency exposure may appear inside packaged products.

Likely exposure

Exposure is most likely in Java applications or vendor products bundling Bouncy Castle JCE Provider 1.55 or earlier and using ECIES with ECB mode. Systems merely carrying the library but not using that configuration may have lower practical exposure.

Exploitation context

No provided source states active exploitation, and the CVE is not listed as KEV. The available evidence describes unsafe cryptographic mode support, not a public attack chain. Exploitability depends on application-specific use of ECIES and attacker access to relevant encrypted data flows.

Researcher notes

The source bundle is sparse: no CVSS, CWE, exploit status, or detailed affected CPEs are provided. The strongest technical fact is that Bouncy Castle removed ECB support from ECIES. Validate real exposure by dependency version and actual ECIES mode usage, not by package presence alone.

Mitigation direction

  • Upgrade Bouncy Castle JCE Provider beyond version 1.55 where feasible.
  • Apply vendor-supported updates from affected platform or product maintainers.
  • Check Red Hat, Oracle, and NetApp guidance for packaged dependency exposure.
  • Remove or replace ECIES configurations that request ECB mode.
  • Document any systems that cannot be upgraded and track vendor guidance.

Validation and detection

  • Inventory Java dependencies for Bouncy Castle JCE Provider version 1.55 or earlier.
  • Review application code and configuration for ECIES usage with ECB mode.
  • Check vendor product versions against Red Hat, Oracle, and NetApp advisories.
  • Confirm upgraded libraries no longer allow ECIES with ECB mode.
  • Record compensating controls where dependency replacement is not immediately possible.
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-1000352 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.