Access of Uninitialized Pointer Affecting openssl-debugsource package, versions <1:3.5.5-1.amzn2023.0.4


Severity

Recommended
high

Based on Amazon Linux security rating.

Threat Intelligence

EPSS
0.02% (7th 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 IDSNYK-AMZN2023-OPENSSLDEBUGSOURCE-16068087
  • published15 Apr 2026
  • disclosed7 Apr 2026

Introduced: 7 Apr 2026

NewCVE-2026-31790  (opens in a new tab)
CWE-824  (opens in a new tab)

How to fix?

Upgrade Amazon-Linux:2023 openssl-debugsource to version 1:3.5.5-1.amzn2023.0.4 or higher.
This issue was patched in ALAS2023-2026-1586.

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 Amazon-Linux. See How to fix? for Amazon-Linux:2023 relevant fixed versions and status.

Issue summary: Applications using RSASVE key encapsulation to establish a secret encryption key can send contents of an uninitialized memory buffer to a malicious peer.

Impact summary: The uninitialized buffer might contain sensitive data from the previous execution of the application process which leads to sensitive data leakage to an attacker.

RSA_public_encrypt() returns the number of bytes written on success and -1 on error. The affected code tests only whether the return value is non-zero. As a result, if RSA encryption fails, encapsulation can still return success to the caller, set the output lengths, and leave the caller to use the contents of the ciphertext buffer as if a valid KEM ciphertext had been produced.

If applications use EVP_PKEY_encapsulate() with RSA/RSASVE on an attacker-supplied invalid RSA public key without first validating that key, then this may cause stale or uninitialized contents of the caller-provided ciphertext buffer to be disclosed to the attacker in place of the KEM ciphertext.

As a workaround calling EVP_PKEY_public_check() or EVP_PKEY_public_check_quick() before EVP_PKEY_encapsulate() will mitigate the issue.

The FIPS modules in 3.6, 3.5, 3.4, 3.3, 3.1 and 3.0 are affected by this issue.

CVSS Base Scores

version 3.1