# CVE-2022-39952: Path traversal in FortiNAC

> Unauthenticated attackers can execute arbitrary code via crafted HTTP requests due to improper file path control in FortiNAC.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:H/RL:U/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Feb 2023
- **Updated:** 23 Oct 2024
- **Also known as:** GHSA-4wjq-4wff-qw9c

## What is CVE-2022-39952?

CVE-2022-39952 is a critical path traversal vulnerability in Fortinet FortiNAC, published on 16 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A external control of file name or path in Fortinet FortiNAC versions 9.4.0, 9.2.0 through 9.2.5, 9.1.0 through 9.1.7, 8.8.0 through 8.8.11, 8.7.0 through 8.7.6, 8.6.0 through 8.6.5, 8.5.0 through 8.5.4, 8.3.7 may allow an unauthenticated attacker to execute unauthorized code or commands via specifically crafted HTTP request.

Weakness: CWE-668 (Exposure of Resource to Wrong Sphere), CWE-73 (External Control of File Name or Path)

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

It affects 1 product.


Products: Fortinet Fortinac.

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

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

## Is CVE-2022-39952 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-39952 exists.

Public exploit code:

- POC for CVE-2022-39952 (github_poc): https://github.com/horizon3ai/CVE-2022-39952
- PoC for CVE-2022-39952 affecting Fortinet FortiNAC. (github_poc): https://github.com/Chocapikk/CVE-2022-39952
- Write Behinder_webshell to target using CVE-2022-39952 (github_poc): https://github.com/shiyeshu/CVE-2022-39952_webshell
- Fortinet FortiNAC keyUpload.jsp arbitrary file write (metasploit)
- PoC for CVE-2022-39952 affecting Fortinet FortiNAC. (github_poc): https://github.com/dkstar11q/CVE-2022-39952-better
- Fortinet FortiNAC - Arbitrary File Write (nuclei): http/cves/2022/CVE-2022-39952.yaml

## Other vulnerabilities in Fortinet FortiNAC

- [CVE-2023-33299](https://insights.sbomify.com/CVE-2023-33299/): Deserialization in FortiNAC (critical 9.6)
- [CVE-2022-26117](https://insights.sbomify.com/CVE-2022-26117/): Hardcoded credentials in Fortinet FortiNAC (high 8.8)
- [CVE-2022-38375](https://insights.sbomify.com/CVE-2022-38375/): Missing authorization in FortiNAC (high 8.6)
- [CVE-2022-39953](https://insights.sbomify.com/CVE-2022-39953/): Privilege escalation in FortiNAC (high 7.8)
- [CVE-2021-43065](https://insights.sbomify.com/CVE-2021-43065/): Privilege escalation in Fortinet FortiNAC (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-39952 is a critical path traversal vulnerability in Fortinet FortiNAC, published on 16 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-39952 exists.

Affected product: Fortinet FortiNAC. 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-39952/ (Markdown: https://insights.sbomify.com/CVE-2022-39952/index.md)
```

## Sources

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

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