Use of a Broken or Risky Cryptographic Algorithm Affecting gnutls package, versions <0:3.6.8-10.el8_2


Severity

Recommended
medium

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.25% (65th 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 a Broken or Risky Cryptographic Algorithm vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-RHEL8-GNUTLS-3778519
  • published26 Jul 2021
  • disclosed27 Mar 2020

Introduced: 27 Mar 2020

CVE-2020-11501  (opens in a new tab)
CWE-327  (opens in a new tab)

How to fix?

Upgrade RHEL:8 gnutls to version 0:3.6.8-10.el8_2 or higher.
This issue was patched in RHSA-2020:1998.

NVD Description

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

GnuTLS 3.6.x before 3.6.13 uses incorrect cryptography for DTLS. The earliest affected version is 3.6.3 (2018-07-16) because of an error in a 2017-10-06 commit. The DTLS client always uses 32 '\0' bytes instead of a random value, and thus contributes no randomness to a DTLS negotiation. This breaks the security guarantees of the DTLS protocol.

CVSS Scores

version 3.1