Cryptographic Issues Affecting bouncycastle package, versions <1.56-1


Severity

Recommended
0.0
medium
0
10

Snyk's Security Team recommends NVD's CVSS assessment. Learn more

Threat Intelligence

EPSS
0.28% (69th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Cryptographic Issues vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-DEBIANUNSTABLE-BOUNCYCASTLE-278508
  • published4 Jun 2018
  • disclosed4 Jun 2018

Introduced: 4 Jun 2018

CVE-2016-1000339  (opens in a new tab)
CWE-310  (opens in a new tab)

How to fix?

Upgrade Debian:unstable bouncycastle to version 1.56-1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream bouncycastle package and not the bouncycastle package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

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.