# CVE-2023-42791: Path traversal in FortiAnalyzer

> Attackers can execute unauthorized code or commands via crafted HTTP requests exploiting a relative path traversal vulnerability in FortiManager.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:F/RL:X/RC:X`)
- **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:** 20 Feb 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-c2qq-2j48-5pr5

## What is CVE-2023-42791?

CVE-2023-42791 is a high-severity path traversal vulnerability in Fortinet Fortimanager, published on 20 Feb 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A relative path traversal in Fortinet FortiManager version 7.4.0 and 7.2.0 through 7.2.3 and 7.0.0 through 7.0.8 and 6.4.0 through 6.4.12 and 6.2.0 through 6.2.11 allows attacker to execute unauthorized code or commands via crafted HTTP requests.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory), CWE-23 (Relative Path Traversal)

## Which versions are affected by CVE-2023-42791?

It affects 1 product.


Products: Fortinet Fortimanager.

## How do I fix CVE-2023-42791?

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

## Is CVE-2023-42791 being exploited?

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

Public exploit code:

- Exploitations scripts for CVE-2023-42791 and CVE-2024-23666. (github_poc): https://github.com/synacktiv/CVE-2023-42791_CVE-2024-23666

## Other vulnerabilities in Fortinet Fortimanager

- [CVE-2024-47575](https://insights.sbomify.com/CVE-2024-47575/): Fortinet FortiManager Missing Authentication (critical 9.8, exploited in the wild)
- [CVE-2015-3613](https://insights.sbomify.com/CVE-2015-3613/): Privilege escalation in n/a (critical 9.8)
- [CVE-2019-6695](https://insights.sbomify.com/CVE-2019-6695/): Security feature bypass in Fortinet FortiManager (critical 9.8)
- [CVE-2019-17654](https://insights.sbomify.com/CVE-2019-17654/): Cross-site request forgery in Fortinet FortiManager (high 8.8)
- [CVE-2015-3611](https://insights.sbomify.com/CVE-2015-3611/): Command injection in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-42791 and fix it if it is affected.

What it is: CVE-2023-42791 is a high-severity path traversal vulnerability in Fortinet Fortimanager, published on 20 Feb 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-42791 in the wild and no public exploit code.

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

## Sources

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

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