CVE-2017-1000082 json
systemd v233 and earlier fails to safely parse usernames starting with a numeric digit (e.g.
published 2017-07-07 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-1399
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.9%
- EPSS 3.9% chance of exploitation in 30 days, percentile 90%
- public exploits
- 0
- none known
Summary
systemd v233 and earlier fails to safely parse usernames starting with a numeric digit (e.g. "0day"), running the service in question with root privileges rather than the user intended.
Patch / fix
- systemd_project systemd 234
- systemd Debian 14, Debian 13, Debian 12 234-1
debian advisories DEBIAN-CVE-2017-1000082
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2017-1000082 updated cvss 7.2
systemd: fails to parse usernames that start with digits
-
Red Hat Enterprise Linux 7 systemd, libgudev1, systemd-libs, systemd-sysv, systemd-python, systemd-networkd, +2 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
3.88% chance of exploitation in the next 30 days, higher than 90% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 10.0 | AV:N/AC:L/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-269 Improper Privilege Management
References
-
github.com
/systemd/systemd/issues/6237
issue-tracking, patch, third-party-advisory
-
openwall.com
/lists/oss-security/2017/07/02/1
mailing-list, patch, third-party-advisory
-
securitytracker.com
/id/1038839
vdb-entry, third-party-advisory
-
securityfocus.com
/bid/99507
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2017-1000082
- NVD CVE-2017-1000082
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.