Use of a Broken or Risky Cryptographic Algorithm Affecting libopenssl3 package, versions <3.0.1-150400.4.7.1


Severity

Recommended
0.0
high
0
10

Based on SUSE Linux Enterprise Server security rating.

Threat Intelligence

EPSS
0.46% (76th 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-SLES154-LIBOPENSSL3-2944406
  • published7 Jul 2022
  • disclosed6 Jul 2022

Introduced: 6 Jul 2022

CVE-2022-2097  (opens in a new tab)
CWE-327  (opens in a new tab)

How to fix?

Upgrade SLES:15.4 libopenssl3 to version 3.0.1-150400.4.7.1 or higher.

NVD Description

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

AES OCB mode for 32-bit x86 platforms using the AES-NI assembly optimised implementation will not encrypt the entirety of the data under some circumstances. This could reveal sixteen bytes of data that was preexisting in the memory that wasn't written. In the special case of "in place" encryption, sixteen bytes of the plaintext would be revealed. Since OpenSSL does not support OCB based cipher suites for TLS and DTLS, they are both unaffected. Fixed in OpenSSL 3.0.5 (Affected 3.0.0-3.0.4). Fixed in OpenSSL 1.1.1q (Affected 1.1.1-1.1.1p).

References

CVSS Scores

version 3.1