Denial of service via header read timeout omission
Published Jul 21, 2021 · Updated Sep 16, 2024
Denial of service in Pires go-proxyproto before 0.6.0 allows remote attackers to exhaust server resources via TCP connections without PROXY headers. The Listener.Accept path waits indefinitely for a PROXY protocol header because no read deadline is imposed, leaving each connection occupied until it sends data or closes. Any network-facing application that embeds the library and accepts attacker-controlled connections can be starved of connection resources, interrupting service without providing data or code execution.
Summary
What happened
Denial of service in Pires go-proxyproto before 0.6.0 allows remote attackers to exhaust server resources via TCP connections without PROXY headers. The Listener.Accept path waits indefinitely for a PROXY protocol header because no read deadline is imposed, leaving each connection occupied until it sends data or closes. Any network-facing application that embeds the library and accepts attacker-controlled connections can be starved of connection resources, interrupting service without providing data or code execution.
The record
- CVE
- CVE-2021-23409
- Published
- Jul 21, 2021
- Updated
- Sep 16, 2024
- Vendor
- Pires
- Product
- go-proxyproto
- Classifications
- CWE-400, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 21, 2021CVE publishedPublication date reported by the CVE source.
- Sep 16, 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=unspecified <0.6.0
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.
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