Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1588695 - (CVE-2016-1000339) CVE-2016-1000339 bouncycastle: Information leak in AESFastEngine class
CVE-2016-1000339 bouncycastle: Information leak in AESFastEngine class
Status: NEW
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
impact=moderate,public=20180607,repor...
: Security
Depends On: 1589579 1592662 1588700 1588701 1588702 1589578
Blocks: 1588310
  Show dependency treegraph
 
Reported: 2018-06-07 14:01 EDT by Pedro Sampaio
Modified: 2018-10-25 11:41 EDT (History)
64 users (show)

See Also:
Fixed In Version: bouncycastle 1.56
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2018:2669 None None None 2018-09-11 03:57 EDT
Red Hat Product Errata RHSA-2018:2927 None None None 2018-10-16 11:25 EDT

  None (edit)
Description Pedro Sampaio 2018-06-07 14:01:06 EDT
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/8a73f08931450c17c749af067b6a8185abdfd2c0#diff-494fb066bed02aeb76b6c005632943f2
https://github.com/bcgit/bc-java/commit/413b42f4d770456508585c830cfcde95f9b0e93b#diff-54656f860db94b867ba7542430cd2ef0
Comment 1 Pedro Sampaio 2018-06-07 14:09:35 EDT
Created bouncycastle tracking bugs for this issue:

Affects: epel-all [bug 1588700]
Affects: fedora-all [bug 1588702]
Comment 3 Mat Booth 2018-06-07 15:58:43 EDT
(In reply to Pedro Sampaio from comment #1)
> Affects: fedora-all [bug 1588702]

Fedora already carries bouncycastle newer than 1.56, so I will close this bug.
Comment 6 Kurt Seifried 2018-06-10 16:29:23 EDT
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/.
Comment 8 errata-xmlrpc 2018-09-11 03:57:08 EDT
This issue has been addressed in the following products:

  Red Hat JBoss Fuse

Via RHSA-2018:2669 https://access.redhat.com/errata/RHSA-2018:2669
Comment 9 errata-xmlrpc 2018-10-16 11:25:05 EDT
This issue has been addressed in the following products:

  Red Hat Satellite 6.4 for RHEL 7

Via RHSA-2018:2927 https://access.redhat.com/errata/RHSA-2018:2927

Note You need to log in before you can comment on or make changes to this bug.