LiveActive security incident?Get immediate response
CVE Record

CVE-2016-1000339: In the Bouncy Castle JCE Provider version 1.55 and earlier the primary engine class used for AES was AESFas...

In the Bouncy Castle JCE Provider version 1.55 and earlier the primary engine class used for AES was AESFastEngine. Due to the highly table driven approach used in the algorithm it turns out that if the data channel on the CPU can be monitored the lookup table accesses are sufficient to leak information on the AES key being used. There was also a leak in AESEngine although it was substantially less. AESEngine has been modified to remove any signs of leakage (testing carried out on Intel X86-64) and is now the primary AES class for the BC JCE provider from 1.56. Use of AESFastEngine is now only recommended where otherwise deemed appropriate.

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 JCE Provider 1.55 and earlier could leak AES key information through CPU side-channel observations. This is not described as a simple remote compromise, but exposure matters where Java applications use affected Bouncy Castle crypto on systems an attacker can observe closely.

Executive priority

Treat this as a targeted cryptographic exposure, not an internet-wide emergency. Prioritize systems handling sensitive AES keys, regulated data, or multi-tenant workloads, then remediate through standard dependency and vendor update processes.

Technical view

The issue centers on AESFastEngine, the primary AES engine through Bouncy Castle JCE 1.55. Its table-driven AES implementation can reveal key-dependent lookup behavior if the CPU data channel is monitored. AESEngine had a smaller leak and was changed in 1.56, becoming the primary AES class.

Likely exposure

Java applications, products, or appliances embedding Bouncy Castle JCE Provider 1.55 or earlier are the likely exposure. Risk is higher for shared, multi-tenant, or otherwise observable compute environments using AES through the provider.

Exploitation context

The CVE source describes side-channel key leakage requiring CPU data-channel monitoring. The bundle does not cite active exploitation, and KEV status is false. Public advisories from Debian, Red Hat, Ubuntu, Oracle, and NetApp indicate downstream affected deployments and fixes existed.

Researcher notes

Evidence is strongest for Bouncy Castle JCE Provider 1.55 and earlier. The source bundle does not provide CVSS, CWE, exploit proof, or detailed affected-product matrices. Avoid broad product claims beyond listed downstream advisories.

Mitigation direction

  • Inventory applications and appliances for Bouncy Castle JCE Provider 1.55 or earlier.
  • Upgrade Bouncy Castle or vendor packages according to the relevant advisory.
  • Prefer Bouncy Castle 1.56 or later where vendor guidance permits.
  • Review custom code for direct AESFastEngine use.
  • Apply downstream distribution updates from Debian, Red Hat, Ubuntu, Oracle, or NetApp as applicable.

Validation and detection

  • Check dependency manifests and runtime classpaths for bcprov or bouncycastle versions.
  • Confirm the deployed provider version is newer than 1.55 or vendor-patched.
  • Search code for direct references to AESFastEngine.
  • Verify affected OS or product packages match fixed advisory versions.
  • Document shared-hosting or co-residency assumptions for systems using AES keys.
Prepared
Confidence
medium
Sources
10

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-1000339 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
9Source 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.