Information disclosure via AES-NI OCB fencepost error
Published Jul 5, 2022 · Updated Sep 17, 2024
Information disclosure in OpenSSL 1.1.1 through 1.1.1p and 3.0.0 through 3.0.4 allows attackers to reveal 16 plaintext bytes. The aesni_ocb_encrypt and aesni_ocb_decrypt loops use a strict-below branch at an inclusive boundary, skipping the final 16-byte block and producing an incorrect tag. The flaw requires 32-bit x86 AES-NI OCB processing; TLS and DTLS are unaffected, and prior output-buffer data or plaintext is disclosed.
Summary
What happened
Information disclosure in OpenSSL 1.1.1 through 1.1.1p and 3.0.0 through 3.0.4 allows attackers to reveal 16 plaintext bytes. The aesni_ocb_encrypt and aesni_ocb_decrypt loops use a strict-below branch at an inclusive boundary, skipping the final 16-byte block and producing an incorrect tag. The flaw requires 32-bit x86 AES-NI OCB processing; TLS and DTLS are unaffected, and prior output-buffer data or plaintext is disclosed.
The record
- CVE
- CVE-2022-2097
- Published
- Jul 5, 2022
- Updated
- Sep 17, 2024
- Vendor
- Debian
- Product
- Debian GNU/Linux
- Classifications
- CWE-326
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 5, 2022CVE publishedPublication date reported by the CVE source.
- Sep 17, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=10.0
- Affected versionversion=11.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo