CVE-2022-2097: AES OCB fails to encrypt some bytes
AES OCB fails to encrypt some bytes
Other sources
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.
OpenSSL security advisory: https://www.openssl.org/news/secadv/20220705.txt
Upstream fix: https://github.com/openssl/openssl/commit/6ebf6d51596f51d23ccbc17930778d104a57d99c [master] https://github.com/openssl/openssl/commit/919925673d6c9cfed3c1085497f5dfbbed5fc431 [111-stable] https://github.com/openssl/openssl/commit/a98f339ddd7e8f487d6e0088d4a9a42324885a93 [openssl-3.0]
โ Red Hat
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.
All versions of the 18.x, 16.x, and 14.x releases lines.
โ Node.Js
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).
AES OCB mode for 32-bit x86 platforms using the AES-NI assembly optimized implementation will not encrypt the entirety of the data under some circumstances. This could reveal sixteen bytes of data that was pre-existing 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.
โ GitHub
AES OCB mode for 32-bit x86 platforms using the AES-NI assembly optimized 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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
redhat/opensslto a version that resolves this vulnerability.Fixed in 1:1.1.1k-7.el8_6 - Upgrade
Upgrade
redhat/opensslto a version that resolves this vulnerability.Fixed in 1:3.0.1-41.el9_0 - Upgrade
Upgrade
rust/openssl-srcto a version that resolves this vulnerability.Fixed in 111.22.0 - Upgrade
Upgrade
rust/openssl-srcto a version that resolves this vulnerability.Fixed in 300.0.9 - Upgrade
Upgrade
redhat/opensslto a version that resolves this vulnerability.Fixed in 1.1.1 - Upgrade
Upgrade
redhat/opensslto a version that resolves this vulnerability.Fixed in 3.0.5 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 1.0.1-2 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 1.1.1k-20 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 20240223gitedc6681206c1-1 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 1.1.1k-12 - Upgrade
Upgrade
debian/opensslto a version that resolves this vulnerability.Fixed in 3.0.20-1~deb12u2Fixed in 3.0.22-1~deb12u2Fixed in 3.5.7-1~deb13u2Fixed in 3.5.7-1~deb13u3Fixed in 3.6.5-1 - Upgrade
Upgrade
alpine/opensslto a version that resolves this vulnerability.Fixed in 1.1.1q-r0 - Upgrade
Upgrade
alpine/opensslto a version that resolves this vulnerability.Fixed in 3.0.5-r0 - Upgrade
Upgrade
alpine/openssl1.1-compatto a version that resolves this vulnerability.Fixed in 1.1.1q-r0 - Upgrade
Upgrade
alpine/openssl3to a version that resolves this vulnerability.Fixed in 3.0.5-r0 - Upgrade
Upgrade
debian/opensslto a version that resolves this vulnerability.Fixed in 3.0.5-1 - Upgrade
Upgrade
OpenSSLto a version that resolves this vulnerability.Fixed in 1.1.1q - Upgrade
Upgrade
OpenSSLto a version that resolves this vulnerability.Fixed in 3.0.5
Event History
Parent advisories
This vulnerability appears in the following advisories.
Frequently Asked Questions
What is the severity of CVE-2022-2097?
The severity of CVE-2022-2097 is high.
Which platforms are affected by CVE-2022-2097?
CVE-2022-2097 affects 32-bit x86 platforms.
What is the impacted software for CVE-2022-2097?
The impacted software for CVE-2022-2097 is OpenSSL.
How can I fix CVE-2022-2097?
To fix CVE-2022-2097, update OpenSSL to version 1.1.1 or higher.
Where can I find more information about CVE-2022-2097?
For more information about CVE-2022-2097, you can refer to the following references: [Link 1](https://security-tracker.debian.org/tracker/CVE-2022-1292), [Link 2](https://nvd.nist.gov/vuln/detail/CVE-2022-1292), [Link 3](https://security-tracker.debian.org/tracker/CVE-2022-2068).