# CVE-2024-3497: Directory Traversal Remote Code Execution Vulnerability

> Attackers can exploit a path traversal flaw in the web server to overwrite files or add new ones, leading to remote code execution on Toshiba MFPs.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Jun 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-pq34-fr9m-wf7m

## What is CVE-2024-3497?

CVE-2024-3497 is a high-severity path traversal vulnerability in Toshiba Tec e-Studio multi-function peripheral (MFP), published on 14 Jun 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Path traversal vulnerability in the web server of the Toshiba printer enables attacker to overwrite orginal files or add new ones to the printer. As for the affected products/models/versions, see the reference URL.

Weakness: CWE-23 (Relative Path Traversal)

## Which versions are affected by CVE-2024-3497?


## How do I fix CVE-2024-3497?

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

## Is CVE-2024-3497 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-3497 and fix it if it is affected.

What it is: CVE-2024-3497 is a high-severity path traversal vulnerability in Toshiba Tec e-Studio multi-function peripheral (MFP), published on 14 Jun 2024. 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-2024-3497 in the wild and no public exploit code.

Affected product: Toshiba Tec e-Studio multi-function peripheral (MFP). 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-2024-3497/ (Markdown: https://insights.sbomify.com/CVE-2024-3497/index.md)
```

## Sources

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

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