Skip to content
Noroxi
NVD / CVE Program· CNA mitre

CVE-2018-6954: systemd-tmpfiles in systemd through 237 mishandles symlinks present in non-terminal path components, which allows local users to obtain…

HighCVSS 7.8 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 31/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.52% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: systemd (Debian:12) 238-1; systemd (openSUSE:Leap 15.0) 234-lp150.20.12.1; systemd-mini (openSUSE:Leap 15.0) 234-lp150.20.12.1.

Low priority for now. Upgrade to systemd (Debian:12) 238-1; systemd (openSUSE:Leap 15.0) 234-lp150.20.12.1; systemd-mini (openSUSE:Leap 15.0) 234-lp150.20.12.1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

systemd-tmpfiles in systemd through 237 mishandles symlinks present in non-terminal path components, which allows local users to obtain ownership of arbitrary files via vectors involving creation of a directory and a file under that directory, and later replacing that directory with a symlink. This occurs even if the fs.protected_symlinks sysctl is turned on.

Published
Feb 13, 2018
Updated
Jun 16, 2026
EPSS
0.5% · 45th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.5%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2018-6954

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
systemd projectsystemd
canonicalubuntu linux
opensuseleap

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • canonical ubuntu linux16.04
  • canonical ubuntu linux18.04
  • canonical ubuntu linux18.10
  • opensuse leap42.3
  • systemd project systemdup to 237 inclusive

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12systemdbefore 238-1238-1
openSUSE:Leap 15.0systemdbefore 234-lp150.20.12.1234-lp150.20.12.1
openSUSE:Leap 15.0systemd-minibefore 234-lp150.20.12.1234-lp150.20.12.1
openSUSE:Tumbleweedsystemdbefore 249.4-2.2249.4-2.2
SUSE:Linux Enterprise Module for Basesystem 15systemdbefore 234-24.20.1234-24.20.1
SUSE:OpenStack Cloud 7systemdbefore 228-150.66.4228-150.66.4

Other highest-scoring records for the same primary product.

  • CVE-2017-9445In systemd through 233, certain sizes passed to dns_packet_new in systemd-resolved can cause it to allocate a buffer that's too small.
    48Plan
  • CVE-2018-21029systemd 239 through 245 accepts any certificate signed by a trusted certificate authority for DNS Over TLS.
    40Plan
  • CVE-2015-7510Stack-based buffer overflow in the getpwnam and getgrnam functions of the NSS module nss-mymachines in systemd.
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2017-15908Oct 26, 2017 · In systemd 223 through 235, a remote DNS server can respond with a custom crafted DNS NSEC resource record to trigger an infinite loop in…
    37Monitor
  • ← EarlierCVE-2017-18078Jan 29, 2018 · systemd-tmpfiles in systemd before 237 attempts to support ownership/permission changes on hardlinked files even if the…
    31Monitor
  • Later →CVE-2018-1049Feb 16, 2018 · In systemd prior to 234 a race condition exists between .mount and .automount units such that automount requests from kernel may not be…
    25Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:systemd238-1 · Debian:12Package registry (OSV)
opensuse:systemd234-lp150.20.12.1 · openSUSE:Leap 15.0Package registry (OSV)
opensuse:systemd-mini234-lp150.20.12.1 · openSUSE:Leap 15.0Package registry (OSV)
suse:systemd234-24.20.1 · SUSE:Linux Enterprise Module for Basesystem 15Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-primary

References

All records