Local privilege escalation via unchecked setuid failure
Published Sep 20, 2024 · Updated Sep 25, 2024
Unchecked return handling in Pure Data 0.54-0 allows local users to retain elevated privileges when a setuid binary starts. In src/s_main.c, sys_main calls setuid(getuid()) to drop the effective user ID but ignores a failure return, so execution continues with the original elevated identity. The binary must carry the setuid bit, and exploitation requires inducing the privilege-drop call to fail; successful exploitation leaves subsequent process actions privileged.
Summary
What happened
Unchecked return handling in Pure Data 0.54-0 allows local users to retain elevated privileges when a setuid binary starts. In src/s_main.c, sys_main calls setuid(getuid()) to drop the effective user ID but ignores a failure return, so execution continues with the original elevated identity. The binary must carry the setuid bit, and exploitation requires inducing the privilege-drop call to fail; successful exploitation leaves subsequent process actions privileged.
The record
- CVE
- CVE-2023-47480
- Published
- Sep 20, 2024
- Updated
- Sep 25, 2024
- Vendor
- Pure Data
- Product
- Pure Data
- Classifications
- CWE-252, T1548.001
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 20, 2024CVE publishedPublication date reported by the CVE source.
- Sep 25, 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.54-0 <0.54-1
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.
Public exploit references
No public exploit references are available in this record.
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