Debug-log forgery via unescaped RPC input
Published Mar 12, 2020 · Updated Aug 5, 2024
Log injection in bitcoind and Bitcoin-Qt before 0.17.1 allows remote attackers with RPC access to insert arbitrary debug-log data. The HTTP RPC logging path writes attacker-controlled request data to debug.log without properly encoding or escaping it, permitting forged entries. Access to the RPC interface is required, and exploitation can mislead operators or downstream log consumers without changing blockchain or wallet state.
Summary
What happened
Log injection in bitcoind and Bitcoin-Qt before 0.17.1 allows remote attackers with RPC access to insert arbitrary debug-log data. The HTTP RPC logging path writes attacker-controlled request data to debug.log without properly encoding or escaping it, permitting forged entries. Access to the RPC interface is required, and exploitation can mislead operators or downstream log consumers without changing blockchain or wallet state.
The record
- CVE
- CVE-2018-20586
- Published
- Mar 12, 2020
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-116
- 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