CVE-2024-54159 json
stalld through 1.19.7 allows local users to cause a denial of service (file overwrite) via a /tmp/rtthrottle symlink attack.
published last yr. modified 4mo ago also EUVD-2024-52323
- cvss
- 4.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 7%
- public exploits
- 0
- none known
Summary
stalld through 1.19.7 allows local users to cause a denial of service (file overwrite) via a /tmp/rtthrottle symlink attack.
Patch / fix
- stalld Linux Micro 6.1 1.19.8-slfo.1.1_1.1
suse advisories SUSE-SU-2025:20468-1
- stalld openSUSE Tumbleweed 1.19.8-1.1
opensuse advisories openSUSE-SU-2025:14886-1
Is CVE-2024-54159 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2024-54159 updated cvss 4.1
stalld: denial of service
-
Red Hat Enterprise Linux 8 stalld Red Hat Enterprise Linux 9 stalld Red Hat Enterprise Linux 10 stalld Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-9affected: no fix available “Fix deferred”
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
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.18% chance of exploitation in the next 30 days, higher than 7% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.1 | CVSS:3.1/AC:H/AV:L/A:L/C:N/I:L/PR:N/S:C/UI:R |
| CNA | 3.1 | 4.1 | CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:N/I:L/A:L |
Classification
- Weakness
-
- CWE-732 Incorrect Permission Assignment for Critical Resource
References
Sources
- CVE List CVE-2024-54159
- NVD CVE-2024-54159
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.