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

> An attacker can delete arbitrary files via path traversal in the Accounts directory of Razer Central.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Feb 2023
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-354j-5v5h-vj52

## What is CVE-2022-45697?

CVE-2022-45697 is a high-severity path traversal vulnerability in n/a, published on 27 Feb 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Arbitrary File Delete vulnerability in Razer Central before v7.8.0.381 when handling files in the Accounts directory.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

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

It affects 1 product.


Products: Razer Razer Central.

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

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

## Is CVE-2022-45697 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-3513](https://insights.sbomify.com/CVE-2023-3513/): RazerCentralService Unsafe Deserialization Escalation of Privilege (high 7.8)
- [CVE-2023-3514](https://insights.sbomify.com/CVE-2023-3514/): RazerCentralSerivce Unsafe Named Pipe Permission Escalation of Privilege Vulnerability (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-45697 is a high-severity path traversal vulnerability in n/a, published on 27 Feb 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-45697 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-45697/ (Markdown: https://insights.sbomify.com/CVE-2022-45697/index.md)
```

## Sources

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

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