LiveActive security incident?Get immediate response
CVE Record

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

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

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-2097 is an OpenSSL data exposure bug in AES OCB encryption on specific 32-bit x86 systems using AES-NI assembly. Under certain conditions, sixteen bytes may be left unencrypted or reveal old memory. OpenSSL says TLS and DTLS are unaffected.

Executive priority

Treat this as a targeted confidentiality issue, not a broad internet-facing TLS emergency. Prioritize patching affected OpenSSL packages and confirming whether any custom or embedded systems use AES OCB on 32-bit x86.

Technical view

The flaw affects OpenSSL 1.1.1 through 1.1.1p and 3.0.0 through 3.0.4 when AES OCB uses the 32-bit x86 AES-NI optimized implementation. OpenSSL fixed it in 1.1.1q and 3.0.5. The most relevant impact is limited confidentiality loss in applications using AES OCB, especially in-place encryption.

Likely exposure

Exposure is likely limited to systems running affected OpenSSL versions on 32-bit x86 with AES-NI and applications that actually use AES OCB. Standard OpenSSL TLS and DTLS use is reported unaffected by OpenSSL.

Exploitation context

The provided sources do not show CISA KEV listing or confirmed active exploitation. The issue requires a specific OpenSSL mode, platform, and implementation path, which narrows practical exposure but does not eliminate risk for custom encryption workflows.

Researcher notes

Key uncertainty is real-world AES OCB usage in the environment. The source description is specific: incomplete encryption of sixteen bytes, with plaintext disclosure in in-place encryption. Avoid broad TLS conclusions because OpenSSL explicitly states TLS and DTLS are unaffected.

Mitigation direction

  • Upgrade OpenSSL 3.0.x deployments to 3.0.5 or later.
  • Upgrade OpenSSL 1.1.1 deployments to 1.1.1q or later.
  • Apply distribution or vendor security updates where OpenSSL is packaged.
  • Check vendor advisories for embedded, appliance, and third-party product dependencies.
  • Prioritize systems using AES OCB or custom cryptographic workflows.

Validation and detection

  • Inventory OpenSSL versions across servers, containers, appliances, and build images.
  • Identify any 32-bit x86 deployments using AES-NI-capable OpenSSL builds.
  • Review applications for AES OCB usage rather than assuming TLS exposure.
  • Confirm affected versions were replaced by fixed vendor packages.
  • Document residual third-party product dependencies awaiting vendor fixes.
Prepared
Confidence
high
Sources
8

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2022-2097 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
14Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
OpenSSLOpenSSLFixed 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)Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.