TLS data modification via predictable RC4-MD5 MAC key
Published May 3, 2022 · Updated Sep 17, 2024
Cryptographic integrity failure in OpenSSL 3.0.0 through 3.0.2 allows man-in-the-middle attackers to modify RC4-MD5 TLS data. The rc4_hmac_md5_set_ctx_params function looks up the TLS AAD parameter instead of the supplied MAC-key parameter, making the MAC key predictable. Exploitation requires a non-default weak-cipher build, the legacy provider, security level 0, pre-TLS 1.3, and negotiated RC4-MD5; encrypted data remains confidential.
Summary
What happened
Cryptographic integrity failure in OpenSSL 3.0.0 through 3.0.2 allows man-in-the-middle attackers to modify RC4-MD5 TLS data. The rc4_hmac_md5_set_ctx_params function looks up the TLS AAD parameter instead of the supplied MAC-key parameter, making the MAC key predictable. Exploitation requires a non-default weak-cipher build, the legacy provider, security level 0, pre-TLS 1.3, and negotiated RC4-MD5; encrypted data remains confidential.
The record
- CVE
- CVE-2022-1434
- Published
- May 3, 2022
- Updated
- Sep 17, 2024
- Vendor
- OpenSSL Project
- Product
- OpenSSL
- Classifications
- CWE-327, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 3, 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=Fixed in OpenSSL 3.0.3 (Affected 3.0.0,3.0.1,3.0.2)
What conditions does exploitation require?
What is affected?
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