Use of a Broken or Risky Cryptographic Algorithm Affecting openssl-debugsource package, versions <1:1.1.1k-7.el8_6


Severity

Recommended
0.0
medium
0
10

Based on Rocky Linux security rating.

Threat Intelligence

Exploit Maturity
Not Defined
EPSS
0.68% (80th 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-ROCKY8-OPENSSLDEBUGSOURCE-3201661
  • published5 Jan 2023
  • disclosed5 Jul 2022

Introduced: 5 Jul 2022

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

How to fix?

Upgrade Rocky-Linux:8 openssl-debugsource to version 1:1.1.1k-7.el8_6 or higher.
This issue was patched in RLSA-2022:5818.

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl-debugsource package and not the openssl-debugsource package as distributed by Rocky-Linux. See How to fix? for Rocky-Linux:8 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