Process crash via unterminated stack-buffer copy
Published Jun 1, 2023 · Updated Jan 10, 2025
Stack buffer overflow in OpenSUSE libeconf before 0.5.2 allows local users to crash a consuming process via malformed configuration content. In econf_writeFile, strncpy copies comment_before_key into an 8,192-byte stack buffer without guaranteeing NUL termination, so strsep reads past the buffer. An application must load attacker-controlled configuration content and invoke file writing; the supported consequence is a process crash.
Summary
What happened
Stack buffer overflow in OpenSUSE libeconf before 0.5.2 allows local users to crash a consuming process via malformed configuration content. In econf_writeFile, strncpy copies comment_before_key into an 8,192-byte stack buffer without guaranteeing NUL termination, so strsep reads past the buffer. An application must load attacker-controlled configuration content and invoke file writing; the supported consequence is a process crash.
The record
- CVE
- CVE-2023-32181
- Published
- Jun 1, 2023
- Updated
- Jan 10, 2025
- Vendor
- OpenSUSE
- Product
- libeconf
- Classifications
- CWE-120, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 1, 2023CVE publishedPublication date reported by the CVE source.
- Jan 10, 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
- econf_writeFile stack-overflow 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