# CVE-2022-25643: Path traversal in n/a

> A local attacker can delete arbitrary files with root privileges via a crafted socket path in seatd-launch when setuid root is enabled.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Feb 2022
- **Updated:** 3 Aug 2024
- **Also known as:** DEBIAN-CVE-2022-25643, GHSA-m93q-8wxv-xgc5, openSUSE-SU-2024:11875-1

## What is CVE-2022-25643?

CVE-2022-25643 is a critical path traversal vulnerability in n/a, published on 22 Feb 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

seatd-launch in seatd 0.6.x before 0.6.4 allows removing files with escalated privileges when installed setuid root. The attack vector is a user-supplied socket pathname.

Weakness: CWE-668 (Exposure of Resource to Wrong Sphere)

## Which versions are affected by CVE-2022-25643?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `seatd` | openSUSE:Tumbleweed | All versions | 0.6.4-1.1 |

Products: Seatd Project Seatd.

## How do I fix CVE-2022-25643?

Upgrade to a fixed version.

## Is CVE-2022-25643 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-41387](https://insights.sbomify.com/CVE-2021-41387/): Privilege escalation in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-25643 and fix it if it is affected.

What it is: CVE-2022-25643 is a critical path traversal vulnerability in n/a, published on 22 Feb 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-25643 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-2022-25643/ (Markdown: https://insights.sbomify.com/CVE-2022-25643/index.md)
```

## Sources

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

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