# CVE-2024-54159: Path traversal in n/a

> Local attackers can overwrite arbitrary files via symlink attacks in stalld, causing denial of service and data modification.

- **Severity:** Medium 4.1 (`CVSS:3.1/AC:H/AV:L/A:L/C:N/I:L/PR:N/S:C/UI:R`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 29 Nov 2024
- **Updated:** 3 Dec 2024
- **Also known as:** GHSA-x839-278f-vq33, SUSE-SU-2025:20468-1, openSUSE-SU-2025:14886-1

## What is CVE-2024-54159?

CVE-2024-54159 is a medium-severity path traversal vulnerability in n/a, published on 29 Nov 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

stalld through 1.19.7 allows local users to cause a denial of service (file overwrite) via a /tmp/rtthrottle symlink attack.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2024-54159?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `stalld` | SUSE:Linux Micro 6.1 | All versions | 1.19.8-slfo.1.1_1.1 |
| `stalld` | openSUSE:Tumbleweed | All versions | 1.19.8-1.1 |

## How do I fix CVE-2024-54159?

Apply the vendor's patch.

## Is CVE-2024-54159 being exploited?

There is no known exploitation of CVE-2024-54159 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-54159 and fix it if it is affected.

What it is: CVE-2024-54159 is a medium-severity path traversal vulnerability in n/a, published on 29 Nov 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-54159 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-54159/ (Markdown: https://insights.sbomify.com/CVE-2024-54159/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-54159
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-54159
- OSV: https://osv.dev/vulnerability/CVE-2024-54159

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-54159/
Summaries are generated and may contain mistakes; the official description above is the record.