Description
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.
Problem types
CWE-754 Improper Check for Unusual or Exceptional Conditions
Product status
3.6.0 (semver) before 3.6.2
3.5.0 (semver) before 3.5.6
3.4.0 (semver) before 3.4.5
3.3.0 (semver) before 3.3.7
3.0.0 (semver) before 3.0.20
Credits
Simo Sorce (Red Hat)
Nikola Pajkovsky
References
openssl-library.org/news/secadv/20260407.txt (OpenSSL Advisory)
github.com/...ommit/abd8b2eec7e3f3fda60ecfb68498b246b52af482 (3.6.2 git commit)
github.com/...ommit/001e01db3e996e13ffc72386fe79d03a6683b5ac (3.5.6 git commit)
github.com/...ommit/d5f8e71cd0a54e961d0c3b174348f8308486f790 (3.4.5 git commit)
github.com/...ommit/b922e24e5b23ffb9cb9e14cadff23d91e9f7e406 (3.3.7 git commit)
github.com/...ommit/eed200f58cd8645ed77e46b7e9f764e284df379e (3.0.20 git commit)