CVE-2016-1000339
published 2018-06-04CVE-2016-1000339: 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…
PriorityP427medium5.3CVSS 3.0
AVNACLPRNUINSUCLINAN
EPSS
2.70%
84.2th percentile
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.
Affected
3 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| bouncycastle | bc-java | <= 1.55 | — |
| debian | bouncycastle | < bouncycastle 1.56-1 (bookworm) | bouncycastle 1.56-1 (bookworm) |
| debian | debian_linux | — | — |
CVSS provenance
nvdv3.05.3MEDIUMCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
nvdv2.05.0MEDIUMAV:N/AC:L/Au:N/C:P/I:N/A:N
osv5.3MEDIUM
vendor_debian5.3MEDIUM
vendor_redhat5.3MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
Moderate severity vulnerability that affects org.bouncycastle:bcprov-jdk14 and org.bouncycastle:bcprov-jdk15
osv·2018-10-17
CVE-2016-1000339 [MEDIUM] Moderate severity vulnerability that affects org.bouncycastle:bcprov-jdk14 and org.bouncycastle:bcprov-jdk15
Moderate severity vulnerability that affects org.bouncycastle:bcprov-jdk14 and org.bouncycastle:bcprov-jdk15
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.
GHSA
Moderate severity vulnerability that affects org.bouncycastle:bcprov-jdk14 and org.bouncycastle:bcprov-jdk15
ghsa·2018-10-17
CVE-2016-1000339 [MEDIUM] Moderate severity vulnerability that affects org.bouncycastle:bcprov-jdk14 and org.bouncycastle:bcprov-jdk15
Moderate severity vulnerability that affects org.bouncycastle:bcprov-jdk14 and org.bouncycastle:bcprov-jdk15
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.
OSV
CVE-2016-1000339: In the Bouncy Castle JCE Provider version 1
osv·2018-06-04·CVSS 5.3
CVE-2016-1000339 [MEDIUM] CVE-2016-1000339: In the Bouncy Castle JCE Provider version 1
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.
Ubuntu
Bouncy Castle vulnerabilities
vendor_ubuntu·2018-08-01
CVE-2015-6644 Bouncy Castle vulnerabilities
Title: Bouncy Castle vulnerabilities
Summary: Several security issues were fixed in Bouncy Castle.
It was discovered that Bouncy Castle incorrectly handled certain crypto
algorithms. A remote attacker could possibly use these issues to obtain
sensitive information, including private keys.
Instructions: In general, a standard system update will make all the necessary changes.
Red Hat
bouncycastle: Information leak in AESFastEngine class
vendor_redhat·2018-06-07·CVSS 5.3
CVE-2016-1000339 [MEDIUM] CWE-200 bouncycastle: Information leak in AESFastEngine class
bouncycastle: Information leak in AESFastEngine class
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.
Statement: This issue affects the versions of bouncycastle as shipped with Red Hat Subscription
Debian
CVE-2016-1000339: bouncycastle - In the Bouncy Castle JCE Provider version 1.55 and earlier the primary engine cl...
vendor_debian·2016·CVSS 5.3
CVE-2016-1000339 [MEDIUM] CVE-2016-1000339: bouncycastle - In the Bouncy Castle JCE Provider version 1.55 and earlier the primary engine cl...
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.
Scope: local
bookworm: resolved (fixed in 1.56-1)
bullseye: resolved (fixed in 1.56-1)
forky: resolved (fixed in 1.56-1)
sid: resolved (fixed in 1.56-1
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2016-1000339 bouncycastle: Information leak in AESFastEngine class [epel-all]
bugzilla·2018-06-07·CVSS 5.3
CVE-2016-1000339 [MEDIUM] CVE-2016-1000339 bouncycastle: Information leak in AESFastEngine class [epel-all]
CVE-2016-1000339 bouncycastle: Information leak in AESFastEngine class [epel-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of epel-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects multiple supported versio
Bugzilla
CVE-2016-1000339 bouncycastle: Information leak in AESFastEngine class [fedora-all]
bugzilla·2018-06-07·CVSS 5.3
CVE-2016-1000339 [MEDIUM] CVE-2016-1000339 bouncycastle: Information leak in AESFastEngine class [fedora-all]
CVE-2016-1000339 bouncycastle: Information leak in AESFastEngine class [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects multiple supported ve
Bugzilla
CVE-2016-1000339 bouncycastle: Information leak in AESFastEngine class
bugzilla·2018-06-07·CVSS 5.3
CVE-2016-1000339 [MEDIUM] CVE-2016-1000339 bouncycastle: Information leak in AESFastEngine class
CVE-2016-1000339 bouncycastle: Information leak in AESFastEngine class
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.
Upstream patch:
https://github.com/bcgit/bc-java/commit/8a73f08931450c17c749a
https://access.redhat.com/errata/RHSA-2018:2669https://access.redhat.com/errata/RHSA-2018:2927https://github.com/bcgit/bc-java/commit/413b42f4d770456508585c830cfcde95f9b0e93b#diff-54656f860db94b867ba7542430cd2ef0https://github.com/bcgit/bc-java/commit/8a73f08931450c17c749af067b6a8185abdfd2c0#diff-494fb066bed02aeb76b6c005632943f2https://lists.debian.org/debian-lts-announce/2018/07/msg00009.htmlhttps://security.netapp.com/advisory/ntap-20181127-0004/https://usn.ubuntu.com/3727-1/https://www.oracle.com/security-alerts/cpuoct2020.htmlhttps://access.redhat.com/errata/RHSA-2018:2669https://access.redhat.com/errata/RHSA-2018:2927https://github.com/bcgit/bc-java/commit/413b42f4d770456508585c830cfcde95f9b0e93b#diff-54656f860db94b867ba7542430cd2ef0https://github.com/bcgit/bc-java/commit/8a73f08931450c17c749af067b6a8185abdfd2c0#diff-494fb066bed02aeb76b6c005632943f2https://lists.debian.org/debian-lts-announce/2018/07/msg00009.htmlhttps://security.netapp.com/advisory/ntap-20181127-0004/https://usn.ubuntu.com/3727-1/https://www.oracle.com/security-alerts/cpuoct2020.html
2018-06-04
Published