CVE-2022-2097: AES OCB fails to encrypt some bytes

Published Jul 5, 2022
ยท
Updated

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

67 affected componentsFixes available
redhat/openssl<1:1.1.1k-7.el8_6
1:1.1.1k-7.el8_6
redhat/openssl<1:3.0.1-41.el9_0
1:3.0.1-41.el9_0
IBM Cognos Analytics<=12.0.0-12.0.1
IBM Cognos Analytics<=11.2.0-11.2.4 FP2
IBM Cognos Analytics<=11.1.1-11.1.7 FP7
rust/openssl-src<111.22.0
111.22.0
rust/openssl-src>=300.0.0<300.0.9
300.0.9
OpenSSL OpenSSL>=1.1.1<1.1.1q
OpenSSL OpenSSL>=3.0.0<3.0.5
Fedoraproject Fedora=35
Fedoraproject Fedora=36
NetApp Active Iq Unified Manager Vmware Vsphere
NetApp Clustered Data Ontap Antivirus Connector
NetApp H300s Firmware
NetApp H300s Firmware
NetApp H500s Firmware
NetApp H500s
NetApp H700s Firmware
NetApp H700s
NetApp H410s Firmware
NetApp H410s
NetApp H410c Firmware
NetApp H410c
Siemens Sinec Ins<1.0
Siemens Sinec Ins=1.0
Siemens Sinec Ins=1.0-sp1
Siemens Sinec Ins=1.0-sp2
Debian Debian Linux=10.0
Debian Debian Linux=11.0
redhat/openssl<1.1.1
1.1.1
redhat/openssl<3.0.5
3.0.5
Microsoft azl3 hvloader 1.0.1-2<1.0.1-2
1.0.1-2
Microsoft cbl2 openssl 1.1.1k-20<1.1.1k-20
1.1.1k-20
Microsoft azl3 edk2 20240223gitedc6681206c1-1<20240223gitedc6681206c1-1
20240223gitedc6681206c1-1
Microsoft cm1 openssl 1.1.1k-12<1.1.1k-12
1.1.1k-12
Microsoft azl3 hvloader 1.0.1-1<1.0.1-2
1.0.1-2
Microsoft azl3 edk2 20230301gitf80f052277c8-37<20240223gitedc6681206c1-1
20240223gitedc6681206c1-1
All of the following
NetApp H300s Firmware
NetApp H300s Firmware
All of the following
NetApp H500s Firmware
NetApp H500s
All of the following
NetApp H700s Firmware
NetApp H700s
All of the following
NetApp H410s Firmware
NetApp H410s
All of the following
NetApp H410c Firmware
NetApp H410c
debian/openssl<3.0.5-1
3.0.5-1
debian/openssl<3.0.5-1
3.0.5-1
debian/openssl<3.0.5-1
3.0.5-1
debian/openssl
3.0.20-1~deb12u23.0.22-1~deb12u23.5.7-1~deb13u23.5.7-1~deb13u33.6.5-1
alpine/openssl>=1.1.1<1.1.1q-r0
1.1.1q-r0
alpine/openssl>=1.1.1<1.1.1q-r0
1.1.1q-r0
alpine/openssl>=1.1.1<1.1.1q-r0
1.1.1q-r0
alpine/openssl>=1.1.1<1.1.1q-r0
1.1.1q-r0
alpine/openssl>=1.1.1<3.0.5-r0
3.0.5-r0
alpine/openssl>=1.1.1<3.0.5-r0
3.0.5-r0
alpine/openssl>=1.1.1<3.0.5-r0
3.0.5-r0
alpine/openssl>=1.1.1<3.0.5-r0
3.0.5-r0
alpine/openssl>=1.1.1<3.0.5-r0
3.0.5-r0
alpine/openssl>=1.1.1<3.0.5-r0
3.0.5-r0
alpine/openssl>=1.1.1<3.0.5-r0
3.0.5-r0
alpine/openssl>=1.1.1<3.0.5-r0
3.0.5-r0
alpine/openssl1.1-compat<1.1.1q-r0
1.1.1q-r0
alpine/openssl1.1-compat<1.1.1q-r0
1.1.1q-r0
alpine/openssl3<3.0.5-r0
3.0.5-r0
alpine/openssl3<3.0.5-r0
3.0.5-r0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade redhat/openssl to a version that resolves this vulnerability.

    Fixed in 1:1.1.1k-7.el8_6
  2. Upgrade

    Upgrade redhat/openssl to a version that resolves this vulnerability.

    Fixed in 1:3.0.1-41.el9_0
  3. Upgrade

    Upgrade rust/openssl-src to a version that resolves this vulnerability.

    Fixed in 111.22.0
  4. Upgrade

    Upgrade rust/openssl-src to a version that resolves this vulnerability.

    Fixed in 300.0.9
  5. Upgrade

    Upgrade redhat/openssl to a version that resolves this vulnerability.

    Fixed in 1.1.1
  6. Upgrade

    Upgrade redhat/openssl to a version that resolves this vulnerability.

    Fixed in 3.0.5
  7. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 1.0.1-2
  8. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 1.1.1k-20
  9. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 20240223gitedc6681206c1-1
  10. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 1.1.1k-12
  11. Upgrade

    Upgrade debian/openssl to 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
  12. Upgrade

    Upgrade alpine/openssl to a version that resolves this vulnerability.

    Fixed in 1.1.1q-r0
  13. Upgrade

    Upgrade alpine/openssl to a version that resolves this vulnerability.

    Fixed in 3.0.5-r0
  14. Upgrade

    Upgrade alpine/openssl1.1-compat to a version that resolves this vulnerability.

    Fixed in 1.1.1q-r0
  15. Upgrade

    Upgrade alpine/openssl3 to a version that resolves this vulnerability.

    Fixed in 3.0.5-r0
  16. Upgrade

    Upgrade debian/openssl to a version that resolves this vulnerability.

    Fixed in 3.0.5-1
  17. Upgrade

    Upgrade OpenSSL to a version that resolves this vulnerability.

    Fixed in 1.1.1q
  18. Upgrade

    Upgrade OpenSSL to a version that resolves this vulnerability.

    Fixed in 3.0.5

Event History

Jul 5, 2022
CVE Published
12:00 AM
CVE Published
via MITREยท10:30 AM
Data Sourced
via MITREยท10:30 AM
DescriptionWeakness
Data Sourced
via NVDยท11:15 AM
DescriptionSeverityWeaknessAffected Software
Data Sourced
via OSVยท11:15 AM
DescriptionSeverityAffected Software
Jul 6, 2022
Exploit Published
via GitHubยท07:18 PM
Advisory Published
via GitHubยท07:57 PM
Jul 7, 2022
Data Sourced
via Red Hatยท12:52 PM
DescriptionSeverityAffected Software
Data Sourced
via Node.jsยท04:00 PM
DescriptionSeverity
Jul 19, 2022
Data Sourced
via Microsoftยท07:00 AM
DescriptionSeverityWeaknessAffected Software
Nov 3, 2022
Data Sourced
08:39 PM
SeverityAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Peer vulnerabilities

Found alongside the following vulnerabilities.

Frequently Asked Questions

1

What is the severity of CVE-2022-2097?

The severity of CVE-2022-2097 is high.

2

Which platforms are affected by CVE-2022-2097?

CVE-2022-2097 affects 32-bit x86 platforms.

3

What is the impacted software for CVE-2022-2097?

The impacted software for CVE-2022-2097 is OpenSSL.

4

How can I fix CVE-2022-2097?

To fix CVE-2022-2097, update OpenSSL to version 1.1.1 or higher.

5

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).

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
ยฉ 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203