# CVE-2025-24350: Path traversal in ctrlX OS - Device Admin

> A remote authenticated attacker can write arbitrary certificates to arbitrary file system paths in ctrlX OS Device Admin via crafted HTTP requests.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Apr 2025
- **Updated:** 30 Apr 2025
- **Also known as:** GHSA-53qh-2v26-q8gx

## What is CVE-2025-24350?

CVE-2025-24350 is a high-severity path traversal vulnerability in Bosch Rexroth AG ctrlX OS - Device Admin, published on 30 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability in the “Certificates and Keys” functionality of the web application of ctrlX OS allows a remote authenticated (low-privileged) attacker to write arbitrary certificates in arbitrary file system paths via a crafted HTTP request.

Weakness: CWE-23 (Relative Path Traversal)

## Which versions are affected by CVE-2025-24350?


## How do I fix CVE-2025-24350?

No fix has been published for CVE-2025-24350 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-24350 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-24350 and fix it if it is affected.

What it is: CVE-2025-24350 is a high-severity path traversal vulnerability in Bosch Rexroth AG ctrlX OS - Device Admin, published on 30 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-24350 in the wild and no public exploit code.

Affected product: Bosch Rexroth AG ctrlX OS - Device Admin. 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-2025-24350/ (Markdown: https://insights.sbomify.com/CVE-2025-24350/index.md)
```

## Sources

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

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