Описание
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 i...
| Релиз | Статус | Примечание |
|---|---|---|
| devel | needed | |
| esm-apps-legacy/xenial | not-affected | 3.0+ only |
| esm-apps/bionic | not-affected | 3.0+ only |
| esm-apps/xenial | not-affected | 3.0+ only |
| esm-infra/focal | not-affected | 3.0+ only |
| jammy | not-affected | 3.0+ only |
| noble | needed | |
| questing | ignored | end of life, was needed |
| resolute | needed | |
| upstream | needs-triage |
Показывать по
| Релиз | Статус | Примечание |
|---|---|---|
| devel | not-affected | uses system openssl |
| esm-apps-legacy/xenial | not-affected | 3.0+ only |
| esm-apps/bionic | not-affected | 3.0+ only |
| esm-apps/focal | not-affected | uses system openssl |
| esm-apps/jammy | not-affected | 3.0+ only |
| esm-apps/noble | not-affected | uses system openssl |
| esm-apps/resolute | not-affected | uses system openssl |
| esm-apps/xenial | not-affected | 3.0+ only |
| esm-infra-legacy/trusty | not-affected | uses system openssl |
| jammy | not-affected | 3.0+ only |
Показывать по
| Релиз | Статус | Примечание |
|---|---|---|
| devel | released | 3.5.5-1ubuntu3 |
| esm-infra-legacy/trusty | not-affected | 3.0+ only |
| esm-infra-legacy/xenial | not-affected | 3.0+ only |
| esm-infra/bionic | not-affected | 3.0+ only |
| esm-infra/focal | not-affected | 3.0+ only |
| esm-infra/xenial | not-affected | 3.0+ only |
| fips-preview/jammy | needs-triage | |
| fips-updates/bionic | not-affected | 3.0+ only |
| fips-updates/focal | not-affected | 3.0+ only |
| fips-updates/jammy | needs-triage |
Показывать по
| Релиз | Статус | Примечание |
|---|---|---|
| devel | DNE | |
| fips-preview/jammy | needs-triage | |
| fips-updates/jammy | needs-triage | |
| fips-updates/noble | needs-triage | |
| jammy | DNE | |
| noble | DNE | |
| questing | DNE | |
| resolute | DNE | |
| upstream | needs-triage |
Показывать по
| Релиз | Статус | Примечание |
|---|---|---|
| devel | DNE | |
| esm-infra/bionic | not-affected | 3.0+ only |
| jammy | DNE | |
| noble | DNE | |
| questing | DNE | |
| resolute | DNE | |
| upstream | needs-triage |
Показывать по
7.5 High
CVSS3
Связанные уязвимости
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 i...
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 i
Incorrect Failure Handling in RSA KEM RSASVE Encapsulation
Issue summary: Applications using RSASVE key encapsulation to establis ...
7.5 High
CVSS3