Program crash via unbounded recursive sorting
Published Jun 16, 2024 · Updated Aug 2, 2024
Stack overflow in binary_insertion_sort.c in The Algorithms C through e5dad3f allows local users to crash the program via crafted array input. The implementation recursively advances through the array without limiting input size or recursion depth, consuming stack frames until the process faults. The input must reach a locally compiled consumer of this educational source; the demonstrated 50-element case terminates with a segmentation fault, while optimized builds can hang.
Summary
What happened
Stack overflow in binary_insertion_sort.c in The Algorithms C through e5dad3f allows local users to crash the program via crafted array input. The implementation recursively advances through the array without limiting input size or recursion depth, consuming stack frames until the process faults. The input must reach a locally compiled consumer of this educational source; the demonstrated 50-element case terminates with a segmentation fault, while optimized builds can hang.
The record
- CVE
- CVE-2024-38443
- Published
- Jun 16, 2024
- Updated
- Aug 2, 2024
- Vendor
- The Algorithms
- Product
- C
- Classifications
- CWE-121, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 16, 2024CVE publishedPublication date reported by the CVE source.
- Aug 2, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <*
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
- 50-element array crash reproducerproof 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