Use of a Broken or Risky Cryptographic Algorithm Affecting libopenssl-1_0_0-devel package, versions <1.0.2p-3.8.1


Severity

Recommended
0.0
medium
0
10

Based on SUSE Linux Enterprise Server security rating.

Threat Intelligence

EPSS
0.81% (82nd 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-SLES150-LIBOPENSSL100DEVEL-2760566
  • published14 Apr 2022
  • disclosed1 Oct 2018

Introduced: 1 Oct 2018

CVE-2018-0737  (opens in a new tab)
CWE-327  (opens in a new tab)

How to fix?

Upgrade SLES:15.0 libopenssl-1_0_0-devel to version 1.0.2p-3.8.1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream libopenssl-1_0_0-devel package and not the libopenssl-1_0_0-devel package as distributed by SLES. See How to fix? for SLES:15.0 relevant fixed versions and status.

The OpenSSL RSA Key generation algorithm has been shown to be vulnerable to a cache timing side channel attack. An attacker with sufficient access to mount cache timing attacks during the RSA key generation process could recover the private key. Fixed in OpenSSL 1.1.0i-dev (Affected 1.1.0-1.1.0h). Fixed in OpenSSL 1.0.2p-dev (Affected 1.0.2b-1.0.2o).

References