Local privilege escalation via numeric username parsing
Published Jun 3, 2020 · Updated Jun 9, 2025
Improper privilege management in systemd 245 and earlier allows local users to gain elevated privileges through a numeric User= value. The user-util.c UID parser accepts account-name strings with numeric prefixes, so a hexadecimal name such as 0x0 is resolved as the corresponding numeric UID instead of through the account database. Exploitation requires an administrator-created service unit with the crafted User= name, a corresponding account, and attacker control of the executed program; UID 0 yields root execution.
Summary
What happened
Improper privilege management in systemd 245 and earlier allows local users to gain elevated privileges through a numeric User= value. The user-util.c UID parser accepts account-name strings with numeric prefixes, so a hexadecimal name such as 0x0 is resolved as the corresponding numeric UID instead of through the account database. Exploitation requires an administrator-created service unit with the crafted User= name, a corresponding account, and attacker control of the executed program; UID 0 yields root execution.
The record
- CVE
- CVE-2020-13776
- Published
- Jun 3, 2020
- Updated
- Jun 9, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-269, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 3, 2020CVE publishedPublication date reported by the CVE source.
- Jun 9, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
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