dbcve.org
OpenSSLFramework / library

CVE-2022-2097

MEDIUM · 5.3 CVSS v3.1 Published 2022-07-05
Fix available
A fix is available. Upgrade to 1.1.1q / 3.0.5 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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).

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

AES OCB mode for 32-bit x86 platforms using AES-NI assembly optimization fails to encrypt the full data length under certain conditions, exposing 16 bytes of either pre-existing memory content or plaintext (in in-place encryption scenarios). OpenSSL TLS/DTLS are unaffected since OCB cipher suites are not supported.

MitigationUpgrade OpenSSL to version 3.0.5 or 1.1.1q. Organizations using 32-bit x86 systems with AES-NI and OCB mode should prioritize patching and verify cryptographic operations.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
OpenSSLFramework / library
Affected:>= 1.1.1, < 1.1.1q>= 3.0.0, < 3.0.5
FedoraOperating system
Affected:= 35= 36
Debian LinuxOperating system
Affected:= 10.0= 11.0
Active Iq Unified ManagerApplication
Affected:all versions
Clustered Data Ontap Antivirus ConnectorApplication
Affected:all versions
H300s FirmwareOperating system
Affected:all versions
H500s FirmwareOperating system
Affected:all versions
H700s FirmwareOperating system
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify OpenSSL version
    Run 'openssl version' or check the library file version (e.g., /usr/lib/libssl.so.1.1 or libssl.so.3)
    Affected if Installed version is >= 1.1.1 and < 1.1.1q, or >= 3.0.0 and < 3.0.5
  2. Confirm system architecture
    Run 'uname -m' or check for 32-bit x86 environment (i686, i386, or 32-bit kernel on x86_64 hardware)
    Affected if Running on a 32-bit x86 platform (i686 or i386)
  3. Verify AES-NI hardware support
    Check /proc/cpuinfo for 'aes' flag or run 'grep -o aes /proc/cpuinfo'
    Affected if AES-NI instructions are available and potentially being used by OpenSSL
  4. Detect OCB mode cipher usage
    Review application configurations, certificates, or code that uses OpenSSL ciphersuites containing 'OCB' (e.g., aes-128-ocb, aes-256-ocb) or check SSL/TLS configurations for OCB cipher listings
    Affected if Applications or configurations are actively using OCB mode ciphers with OpenSSL on the affected system

A user is affected if they are running a vulnerable OpenSSL version (1.1.1-1.1.1q or 3.0.0-3.0.5) on a 32-bit x86 system with AES-NI support while using OCB mode encryption for in-place operations.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.1.1q / 3.0.5 or later
Fixed in 1.1.1q3.0.5
Interim mitigation

Upgrade OpenSSL to version 3.0.5 or 1.1.1q. Organizations using 32-bit x86 systems with AES-NI and OCB mode should prioritize patching and verify cryptographic operations.

Recommended fix High confidence

OpenSSL 1.1.1q (for 1.1.1 branch) or OpenSSL 3.0.5 (for 3.0 branch)

  1. Identify the OpenSSL version currently installed on the system using 'openssl version' or checking the package manager
  2. For systems using OpenSSL 1.1.1x: upgrade to OpenSSL 1.1.1q or later
  3. For systems using OpenSSL 3.0.x: upgrade to OpenSSL 3.0.5 or later
  4. Verify the upgrade was successful by checking the new version with 'openssl version'
  5. For embedded systems (H300s/H500s/H700s firmware, NetApp connectors, Active IQ Unified Manager): contact the vendor for firmware/software updates that include the OpenSSL patch
  6. For Linux distributions (Fedora, Debian): apply distribution-specific security updates that include the fixed OpenSSL packages
Caveat The vulnerability only affects AES OCB mode which is not used in TLS/DTLS, and OpenSSL does not enable OCB ciphersuites by default - minimal risk expected from upgrade but test in staging if possible

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in OpenSSL Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-2097 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-2097 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data