Certificate validation bypass via uninitialized hostname buffer
Published Feb 27, 2020 · Updated Aug 4, 2024
Improper certificate validation in openfortivpn 1.7.1 through 1.11.0 allows man-in-the-middle attackers to subvert VPN server trust. The ssl_verify_cert function passes an uninitialized common_name buffer to X509_check_host instead of the configured gateway hostname. With OpenSSL 1.0.2 or later, the faulty check rejects valid certificates while a malformed certificate can pass, exposing the client to an impostor server.
Summary
What happened
Improper certificate validation in openfortivpn 1.7.1 through 1.11.0 allows man-in-the-middle attackers to subvert VPN server trust. The ssl_verify_cert function passes an uninitialized common_name buffer to X509_check_host instead of the configured gateway hostname. With OpenSSL 1.0.2 or later, the faulty check rejects valid certificates while a malformed certificate can pass, exposing the client to an impostor server.
The record
- CVE
- CVE-2020-7042
- Published
- Feb 27, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-908, CWE-295, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 27, 2020CVE 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.
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