Skip to content
Fencer Intel
low 3.3

CVE-2012-1174 json

The rm_rf_children function in util.c in the systemd-logind login manager in systemd before 44, when logging out, allows local users to del…

published 2012-07-12 14 y ago modified 2026-06-16 4 mo ago also EUVD-2012-1204

cvss
3.3
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 25%
public exploits
0
none known

Summary

The rm_rf_children function in util.c in the systemd-logind login manager in systemd before 44, when logging out, allows local users to delete arbitrary files via a symlink attack on unspecified files, related to "particular records related with user session."

Patch / fix

  • systemd Debian 14, Debian 13, Debian 12 44-1

debian advisories DEBIAN-CVE-2012-1174

  • systemd-ui openSUSE Tumbleweed 3-1.8
  • systemd openSUSE Tumbleweed 228-17.1

opensuse advisories openSUSE-SU-2024:10112-1openSUSE-SU-2024:10356-1

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-2012-1174 updated cvss 4.7

(systemd-logind): TOCTOU race condition by removing user session

  • Red Hat All currently supported Red Hat products
    not 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

0.32% chance of exploitation in the next 30 days, higher than 25% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • cgit.freedesktop.org http://cgit.freedesktop.org/systemd/systemd/commit/?id=5ebff5337594d690b322078c512eb222d34aaa82 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 3.3 AV:L/AC:M/Au:N/C:N/I:P/A:P

Classification

Weakness
  • CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization

References

Sources

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.