Node crash via out-of-bounds string read
Published Mar 16, 2022 · Updated Aug 3, 2024
Heap-buffer over-read in EOS 2.1.0 allows remote attackers to crash nodeos via the txn_test_gen create_test_accounts HTTP endpoint. A string construction in create_test_accounts calls strlen on a 4,476-byte heap allocation and reads one byte beyond its end. Exploitation requires txn_test_gen_plugin and its HTTP route to be enabled; the demonstrated consequence is process abort, not data access or modification.
Summary
What happened
Heap-buffer over-read in EOS 2.1.0 allows remote attackers to crash nodeos via the txn_test_gen create_test_accounts HTTP endpoint. A string construction in create_test_accounts calls strlen on a 4,476-byte heap allocation and reads one byte beyond its end. Exploitation requires txn_test_gen_plugin and its HTTP route to be enabled; the demonstrated consequence is process abort, not data access or modification.
The record
- CVE
- CVE-2022-26300
- Published
- Mar 16, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 16, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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
- EOSIO issue 10820 reproductionproof 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