Homepage

Information Exposure Affecting foreman-cli package, versions <0:1.18.0.37-1.el7sat

Severity

 Recommended
high

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.33% (72nd 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 IDSNYK-RHEL7-FOREMANCLI-5365819
  • published26 Mar 2023
  • disclosed7 Jun 2018
Report a new vulnerability Found a mistake?

Introduced: 7 Jun 2018

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

How to fix?

Upgrade RHEL:7 foreman-cli to version 0:1.18.0.37-1.el7sat or higher.
This issue was patched in RHSA-2018:2927.

NVD Description

Note: Versions mentioned in the description apply only to the upstream foreman-cli package and not the foreman-cli package as distributed by RHEL. See How to fix? for RHEL:7 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.