Test-process crash via undersized argument array
Published Jul 16, 2024 · Updated Aug 2, 2024
A dynamic stack buffer overflow in Open5GS 2.6.4 test runners allows local users to crash an AddressSanitizer-enabled test process. Test entry points allocate argv_out one pointer too small before abts_main appends arguments and a terminator, causing an eight-byte write beyond the stack array. Reachability requires a local source build and test-suite execution; public evidence does not show exposure in installed network services.
Summary
What happened
A dynamic stack buffer overflow in Open5GS 2.6.4 test runners allows local users to crash an AddressSanitizer-enabled test process. Test entry points allocate argv_out one pointer too small before abts_main appends arguments and a terminator, causing an eight-byte write beyond the stack array. Reachability requires a local source build and test-suite execution; public evidence does not show exposure in installed network services.
The record
- CVE
- CVE-2024-40130
- Published
- Jul 16, 2024
- Updated
- Aug 2, 2024
- Vendor
- Open5GS
- Product
- Open5GS
- Classifications
- CWE-120, CWE-787
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 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=v2.6.4
What conditions does exploitation require?
What is affected?
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
- AddressSanitizer test-suite 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