TLS interception via omitted hostname verification
Published Dec 23, 2021 · Updated Aug 4, 2024
Improper certificate validation in e2guardian 5.4.0 through 5.4.3r allows man-in-the-middle attackers to intercept proxied TLS traffic. Socket::startSslClient sets the TLS SNI hostname but, with OpenSSL 1.1.x, fails to configure that hostname as the certificate verification target. The flaw is reachable only in standalone proxy or transparent-proxy deployments with SSL MITM enabled, where an on-path attacker can present any otherwise valid certificate and read or alter upstream traffic.
Summary
What happened
Improper certificate validation in e2guardian 5.4.0 through 5.4.3r allows man-in-the-middle attackers to intercept proxied TLS traffic. Socket::startSslClient sets the TLS SNI hostname but, with OpenSSL 1.1.x, fails to configure that hostname as the certificate verification target. The flaw is reachable only in standalone proxy or transparent-proxy deployments with SSL MITM enabled, where an on-path attacker can present any otherwise valid certificate and read or alter upstream traffic.
The record
- CVE
- CVE-2021-44273
- Published
- Dec 23, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-295, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 23, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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.
Public exploit references
- wrong.host.badssl.com hostname-mismatch reproductionproof of concept · demonstrated
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