nday
CVE-2016-1000339

Bouncy Castle: cryptographic failureTitle composed by nday; the CVE record has none.

Disclosed . nday has no fix record for it yet; that does not mean no patch exists. None of the four PoC sources lists it. Not in CISA KEV.

why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

cryptographic failure
CWE-310, stated by NVD's analysts
remote, unauthenticated
AV:N, PR:N, UI:N in CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N (CVSS 3.0) from NVD's analysts
network
AV:N in CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N (CVSS 3.0) from NVD's analysts
no authentication required
PR:N in CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N (CVSS 3.0) from NVD's analysts
no user interaction
UI:N in CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N (CVSS 3.0) from NVD's analysts
Bouncy Castle
CPE names NVD's analysts give as vulnerable: a:bouncycastle:bc-java
open-source library / framework
CPE names NVD's analysts give as vulnerable: a:bouncycastle:bc-javathe product type of Bouncy Castle in nday's product registry
stage
DIS
disclosed
cvss
no score yet

Lifecycle

x axis UTC; dot = exact minute, wide bar = date only, hollow = unknown or inferred.
time unknown
DISdisclosed
2018-06-04T13:00Z
PATpatch
no record yet
ANAanalysis
no record yet
POCPoC
no record yet
ITWexploited
no record yet
KEVKEV
no record yet

Summary

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.

Original text of the CVE record (cvelist), shown as published.

Event log

+DISdisclosed

CVE record published by mitre.

src cvelist · nday , bulk import · raw
{
  "id": 161681,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2016-1000339",
  "occurred_at": "2018-06-04T13:00:00Z",
  "observed_at": "2026-11-13T05:36:29.933389Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "state": "PUBLISHED",
    "date_published": "2018-06-04T13:00:00.000Z",
    "assigner_short_name": "mitre"
  }
}

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

Researcher discussion

0 researchers mentioned this in the last 7 days

Posts on X by researchers on nday's list that mention this CVE, shown as posted. nday does not check them.

nday has not collected any post on X by listed researchers that mentions this CVE.

Discussion

0 comments

No comments yet.