CVE-2017-1000082 — systemd v233 and earlier fails to safely parse usernames starting with a numeric digit (e.g. ...
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 3.9% (30-day exploitation probability)+14
- Technical severity (critical)+10
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — www.openwall.com (NIST National Vulnerability Database)
- Documented patch — github.com (NIST National Vulnerability Database)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Systemd Project Systemd).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- Apply the fixed version or the patch documented under Remediation.
- EPSS ahead of 90% of scored CVEs: prioritize it in the patch queue.
- Search available logs for exploit probes matching the vulnerability class (privilege escalation), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Systemd Project | Systemd | ≥ 229 and < 234 | Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 9.8 | CVSS 3.1 | Critical | 3.9 | 5.9 | nvd@nist.gov via NIST National Vulnerability Database |
| 9.8 | CVSS 3.1 | Critical | — | — | GitHub, Inc. via GitHub Security Advisories |
| 10.0 | CVSS 2.0 | High | 10.0 | 10.0 | nvd@nist.gov via NIST National Vulnerability Database |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 3.88%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Fix documented
- Affected products added · systemd project/systemd
- CVSS changed · 9.8
- Source status changed · → Modified
- Record created in this database
- 2017
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 14, 2026 – Oct 14, 2026
- 1× Official description updated · Oct 14, 2026 – Oct 14, 2026
References
6 on the record
Elsewhere on this site
Related CVEs (same products)
- Medium CVE-2026-40225 Incorrect Resource Transfer Between Spheres in Systemd Project Systemd Apr 10, 2026
- Medium CVE-2026-40227 In systemd 260 before 261, a local unprivileged user can trigger an assert via an IPC… Apr 10, 2026
- Medium CVE-2026-40226 In nspawn in systemd 233 through 259 before 260, an escape-to-host action can occur via… Apr 10, 2026
- High CVE-2026-40224 Incorrect Authorization in Systemd Project Systemd Apr 10, 2026
- Low CVE-2026-40228 Incorrect Resource Transfer Between Spheres in Systemd Project Systemd Apr 10, 2026
- Medium CVE-2026-40223 In systemd 258 before 260, a local unprivileged user can trigger an assert when a… Apr 10, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CISA SSVC assessment.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2017-1000082 is "systemd v233 and earlier fails to safely parse usernames starting with a numeric digit (e.g. ...", rated Critical. It affects Systemd (Systemd Project); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 9.8 describes technical severity. EPSS 3.88% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.