Homepage

Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG) Affecting tfm-runtime package, versions <0:4.0-3.el7sat

Severity

 Recommended
high

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.38% (74th 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 Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG) vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-RHEL7-TFMRUNTIME-5376376
  • published26 Mar 2023
  • disclosed7 Jun 2018
Report a new vulnerability Found a mistake?

Introduced: 7 Jun 2018

CVE-2016-1000343  (opens in a new tab)
CWE-338  (opens in a new tab)

How to fix?

Upgrade RHEL:7 tfm-runtime to version 0:4.0-3.el7sat or higher.
This issue was patched in RHSA-2018:2927.

NVD Description

Note: Versions mentioned in the description apply only to the upstream tfm-runtime package and not the tfm-runtime 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 DSA key pair generator generates a weak private key if used with default values. If the JCA key pair generator is not explicitly initialised with DSA parameters, 1.55 and earlier generates a private value assuming a 1024 bit key size. In earlier releases this can be dealt with by explicitly passing parameters to the key pair generator.