Proxy crash via unmapped certificate validation errors
Published Jun 30, 2020 · Updated Aug 4, 2024
Denial of service in Squid 3.1 through 3.5.28, 4.0 through 4.11, and 5.0.1 through 5.0.2 allows remote attackers to crash the proxy. The TLS certificate error path maps unrecognized OpenSSL X509 validation codes to NULL, then passes the missing error name to code that expects a valid string. Reachability requires an OpenSSL-enabled build and a trusted client that causes an HTTPS peer or SSL-Bump server handshake with an attacker-controlled endpoint.
Summary
What happened
Denial of service in Squid 3.1 through 3.5.28, 4.0 through 4.11, and 5.0.1 through 5.0.2 allows remote attackers to crash the proxy. The TLS certificate error path maps unrecognized OpenSSL X509 validation codes to NULL, then passes the missing error name to code that expects a valid string. Reachability requires an OpenSSL-enabled build and a trusted client that causes an HTTPS peer or SSL-Bump server handshake with an attacker-controlled endpoint.
The record
- CVE
- CVE-2020-14058
- Published
- Jun 30, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 30, 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