Remote node crash via oversized receive buffers
Published Mar 12, 2020 · Updated Aug 6, 2024
Memory exhaustion in Bitcoin Core bitcoind and Bitcoin-Qt before 0.10.1 allows remote attackers to crash nodes through P2P messages. The P2P receive path reserved as much as 32 MiB per connection before reading each message payload, letting incomplete messages consume memory across concurrent peers. Any internet-reachable node accepting inbound peer connections is exposed, and successful exhaustion terminates the node without affecting transaction integrity.
Summary
What happened
Memory exhaustion in Bitcoin Core bitcoind and Bitcoin-Qt before 0.10.1 allows remote attackers to crash nodes through P2P messages. The P2P receive path reserved as much as 32 MiB per connection before reading each message payload, letting incomplete messages consume memory across concurrent peers. Any internet-reachable node accepting inbound peer connections is exposed, and successful exhaustion terminates the node without affecting transaction integrity.
The record
- CVE
- CVE-2015-3641
- Published
- Mar 12, 2020
- Updated
- Aug 6, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1499.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 12, 2020CVE publishedPublication date reported by the CVE source.
- Aug 6, 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