Traffic disclosure and tampering via predictable IVs
Published Jan 18, 2022 · Updated Aug 3, 2024
Cryptographic failure in wolfSSL 5.0.0 through 5.1.0 allows remote attackers to read or alter protected traffic via predictable IVs. A misplaced memory-initialization operation in BuildMessage in internal.c overwrites generated record IV bytes with non-random values. Exposure is limited to non-AEAD AES-CBC or DES3 connections using TLS 1.1, TLS 1.2, DTLS 1.1, or DTLS 1.2.
Summary
What happened
Cryptographic failure in wolfSSL 5.0.0 through 5.1.0 allows remote attackers to read or alter protected traffic via predictable IVs. A misplaced memory-initialization operation in BuildMessage in internal.c overwrites generated record IV bytes with non-random values. Exposure is limited to non-AEAD AES-CBC or DES3 connections using TLS 1.1, TLS 1.2, DTLS 1.1, or DTLS 1.2.
The record
- CVE
- CVE-2022-23408
- Published
- Jan 18, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-330
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 18, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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