CoreCVE
Back

MEDIUM

bouncycastle: Information leak in AESFastEngine class

Published Jun 4, 2018

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.

Affected products

Remediation

Red Hat statement

This issue affects the versions of bouncycastle as shipped with Red Hat Subscription Asset Manager 1.x. Red Hat Product Security has rated this issue as having a security impact of Moderate. No update is planned for this product at this time. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/.

Metrics

Weaknesses (2)

CWE-200

Exposure of Sensitive Information

CWE-310

References (13)

Change history (0)

No recorded changes yet.

Sources
CVE.org / MITRE
Status PUBLISHED
Assigner mitre
Published Jun 4, 2018
Updated Aug 6, 2024
Reserved Jun 4, 2018
Link CVE-2016-1000339
CISA Vulnrichment
Updated n/a
NVD
Status Modified
Modified Jun 17, 2026
Link CVE-2016-1000339
Red Hat
Severity Moderate
Public date Jun 7, 2018
Links CVE-2016-1000339 - Bugzilla
GHSA-C8XF-M4FF-JCXJ