CVE-2016-1000339 Details
Description
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.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-310 | Cryptographic Issues | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| bouncycastle bc-java | <= 1.55 |
CPE
Remediation
| |
| debian debian linux | 8.0 |
CPE
Remediation
| |
Change History
11 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | [email protected] |
| May 12, 2025 | CPE Deprecation Remap | [email protected] |
| Nov 21, 2024 | CVE Modified | CVE |
| May 14, 2024 | CVE Modified | [email protected] |
| Oct 20, 2020 | CVE Modified | [email protected] |
| Nov 28, 2018 | CVE Modified | [email protected] |
| Oct 17, 2018 | CVE Modified | [email protected] |
| Sep 12, 2018 | CVE Modified | [email protected] |
| Aug 3, 2018 | CVE Modified | [email protected] |
| Jul 18, 2018 | Initial Analysis | [email protected] |
| Jul 9, 2018 | CVE Modified | [email protected] |