Service crash via long ASCII text decoding
Published Feb 19, 2024 · Updated Feb 13, 2025
Buffer overflow in cbor2 5.5.1 through 5.6.1 allows remote attackers to crash services by supplying CBOR with a long ASCII string. The C decoder's long-text path triggers a CPython error while decoding all-ASCII content, corrupting allocator state instead of returning the string. Exploitation requires an application to pass attacker-controlled CBOR to the affected C decoder; the demonstrated consequence is process termination.
Summary
What happened
Buffer overflow in cbor2 5.5.1 through 5.6.1 allows remote attackers to crash services by supplying CBOR with a long ASCII string. The C decoder's long-text path triggers a CPython error while decoding all-ASCII content, corrupting allocator state instead of returning the string. Exploitation requires an application to pass attacker-controlled CBOR to the affected C decoder; the demonstrated consequence is process termination.
The record
- CVE
- CVE-2024-26134
- Published
- Feb 19, 2024
- Updated
- Feb 13, 2025
- Vendor
- Alex Grönholm
- Product
- cbor2
- Classifications
- CWE-120, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 19, 2024CVE publishedPublication date reported by the CVE source.
- Feb 13, 2025Record 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 5.5.1, < 5.6.2
- Affected versionversion=5.5.1 <5.6.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- GHSA-375g-39jq-vq7m 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