Local information disclosure via incorrect core-dump ACLs
Published Jan 11, 2023 · Updated Nov 3, 2025
Information disclosure in systemd 247 and later allows local users to read privileged process memory through systemd-coredump. The handler ignores fs.suid_dumpable=2 and adds an ACL granting the crashed process's real user read access to a privileged core dump. A local account must start and crash a setuid or capability-bearing program on a libacl-enabled build, exposing secrets held in that process's memory.
Summary
What happened
Information disclosure in systemd 247 and later allows local users to read privileged process memory through systemd-coredump. The handler ignores fs.suid_dumpable=2 and adds an ACL granting the crashed process's real user read access to a privileged core dump. A local account must start and crash a setuid or capability-bearing program on a libacl-enabled build, exposing secrets held in that process's memory.
The record
- CVE
- CVE-2022-4415
- Published
- Jan 11, 2023
- Updated
- Nov 3, 2025
- Vendor
- systemd
- Product
- systemd
- Classifications
- CWE-200, T1003
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 11, 2023CVE publishedPublication date reported by the CVE source.
- Nov 3, 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=systemd >= 247
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
- su_core_shadow_extract.pyproof 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