Client crash via deeply nested JSON configuration
Published Jan 11, 2021 · Updated Aug 4, 2024
Stack overflow in the Aleth Ethereum C++ client 1.8.0 and earlier allows attackers to crash the client via a crafted config.json file. The configuration parser accepts at least 3,764 unmatched opening square brackets and exhausts the process stack, terminating Aleth with a segmentation fault. Exploitation requires Aleth to be started with the malicious file through the --config option; the demonstrated consequence is a client crash.
Summary
What happened
Stack overflow in the Aleth Ethereum C++ client 1.8.0 and earlier allows attackers to crash the client via a crafted config.json file. The configuration parser accepts at least 3,764 unmatched opening square brackets and exhausts the process stack, terminating Aleth with a segmentation fault. Exploitation requires Aleth to be started with the malicious file through the --config option; the demonstrated consequence is a client crash.
The record
- CVE
- CVE-2020-26800
- Published
- Jan 11, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 11, 2021CVE 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.
Public exploit references
- Crafted config.json crash proof of conceptproof of concept · demonstrated
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