OpenSSL up to 1.1.1p/3.0.4 on 32-bit AES OCB Mode missing encryption

Summaryinfo

A vulnerability marked as problematic has been reported in OpenSSL up to 1.1.1p/3.0.4 on 32-bit. The impacted element is an unknown function of the component AES OCB Mode. This manipulation causes missing encryption. This vulnerability is handled as CVE-2022-2097. The attack can be initiated remotely. There is not any exploit available. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability classified as problematic was found in OpenSSL up to 1.1.1p/3.0.4 on 32-bit (Network Encryption Software). Affected by this vulnerability is an unknown code of the component AES OCB Mode. The manipulation with an unknown input leads to a missing encryption vulnerability. The CWE definition for the vulnerability is CWE-311. The product does not encrypt sensitive or critical information before storage or transmission. As an impact it is known to affect confidentiality. The summary by CVE is:

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

The weakness was released 07/05/2022 as 20220705.txt. The advisory is shared at openssl.org. This vulnerability is known as CVE-2022-2097 since 06/16/2022. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1600 for this issue.

The vulnerability scanner Nessus provides a plugin with the ID 211174 (Fedora 37 : openssl (2022-1c20b4dde2)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 1.1.1q or 3.0.5 eliminates this vulnerability. Applying the patch 919925673d6c9cfed3c1085497f5dfbbed5fc431 is able to eliminate this problem. The bugfix is ready for download at git.openssl.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the vulnerability database at Tenable (211174). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Network Encryption Software

Name

• OpenSSL

Version

• 1.1.1
• 1.1.1a
• 1.1.1b
• 1.1.1c
• 1.1.1d
• 1.1.1e
• 1.1.1f
• 1.1.1g
• 1.1.1h
• 1.1.1i
• 1.1.1j
• 1.1.1k
• 1.1.1l
• 1.1.1m
• 1.1.1n
• 1.1.1o
• 1.1.1p
• 3.0.0
• 3.0.1
• 3.0.2
• 3.0.3
• 3.0.4

License

• open-source

Website

• Product: https://www.openssl.org/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion