Use of a Broken or Risky Cryptographic Algorithm Affecting libopenssl1_0_0 package, versions <1.0.2p-3.11.1


Severity

Recommended
0.0
medium
0
10

Based on SUSE Linux Enterprise Server security rating.

Threat Intelligence

EPSS
0.93% (83rd 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-LIBOPENSSL100-2758974
  • published14 Apr 2022
  • disclosed6 Dec 2018

Introduced: 6 Dec 2018

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

How to fix?

Upgrade SLES:15.0 libopenssl1_0_0 to version 1.0.2p-3.11.1 or higher.

NVD Description

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

The OpenSSL DSA signature algorithm has been shown to be vulnerable to a timing side channel attack. An attacker could use variations in the signing algorithm to recover the private key. Fixed in OpenSSL 1.1.1a (Affected 1.1.1). Fixed in OpenSSL 1.1.0j (Affected 1.1.0-1.1.0i). Fixed in OpenSSL 1.0.2q (Affected 1.0.2-1.0.2p).

References

CVSS Scores

version 3.1