Application crash via out-of-bounds terminator write
Published Jun 1, 2023 · Updated May 13, 2025
Stack buffer overflow in openSUSE libeconf before 0.5.2 allows local users to crash applications via malformed configuration files. In lib/getfilecontents.c, read_file finds a comment character with strchr and writes a NUL byte at p+1 without verifying that p+1 remains inside the stack buffer. Exploitation requires a crafted file to be parsed by a consuming process; the grounded impact is an application crash, not code execution.
Summary
What happened
Stack buffer overflow in openSUSE libeconf before 0.5.2 allows local users to crash applications via malformed configuration files. In lib/getfilecontents.c, read_file finds a comment character with strchr and writes a NUL byte at p+1 without verifying that p+1 remains inside the stack buffer. Exploitation requires a crafted file to be parsed by a consuming process; the grounded impact is an application crash, not code execution.
The record
- CVE
- CVE-2023-22652
- Published
- Jun 1, 2023
- Updated
- May 13, 2025
- Vendor
- OpenSUSE
- Product
- libeconf
- Classifications
- CWE-120, T1499.004
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Jun 1, 2023CVE publishedPublication date reported by the CVE source.
- May 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=? <0.5.2
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
- GitHub issue 177 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