# CVE-2022-36302: Path traversal in BF-OS

> An attacker can manipulate file paths to access sensitive resources in Bosch BF-OS, leading to information disclosure.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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:** 1 Aug 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-cfq2-r39h-44gj

## What is CVE-2022-36302?

CVE-2022-36302 is a high-severity path traversal vulnerability in Bosch BF-OS, published on 1 Aug 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

File path manipulation vulnerability in BF-OS version 3.00 up to and including 3.83 allows an attacker to modify the file path to access different resources, which may contain sensitive information.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component), CWE-641 (Improper Restriction of Names for Files and Other Resources)

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

It affects 1 product.


Products: Bosch Bf-Os.

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

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

## Is CVE-2022-36302 being exploited?

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

## Other vulnerabilities in Bosch BF-OS

- [CVE-2022-36301](https://insights.sbomify.com/CVE-2022-36301/): Weak cryptography in BF-OS (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-36302 is a high-severity path traversal vulnerability in Bosch BF-OS, published on 1 Aug 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-36302 in the wild and no public exploit code.

Affected product: Bosch BF-OS. 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-36302/ (Markdown: https://insights.sbomify.com/CVE-2022-36302/index.md)
```

## Sources

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

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