Service interruption via SOCKS5 signed-length overflow
Published Mar 12, 2020 · Updated Aug 5, 2024
Stack-based buffer overflow in Bitcoin Core before 0.15.1 allows remote attackers controlling a SOCKS proxy to interrupt the node. In the SOCKS5 reply parser, a domain-length byte with its high bit set becomes negative as signed char, then expands to a huge unsigned recv() length that overruns a 256-byte stack buffer. The node must use the malicious proxy or connect to its proxy through an interceptable network; the documented consequence is program-stack overwrite and service interruption.
Summary
What happened
Stack-based buffer overflow in Bitcoin Core before 0.15.1 allows remote attackers controlling a SOCKS proxy to interrupt the node. In the SOCKS5 reply parser, a domain-length byte with its high bit set becomes negative as signed char, then expands to a huge unsigned recv() length that overruns a 256-byte stack buffer. The node must use the malicious proxy or connect to its proxy through an interceptable network; the documented consequence is program-stack overwrite and service interruption.
The record
- CVE
- CVE-2017-18350
- Published
- Mar 12, 2020
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 12, 2020CVE publishedPublication date reported by the CVE source.
- Aug 5, 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