# CVE-2023-31476: Path traversal in n/a

> Attackers can create arbitrary empty files on GL.iNet router filesystems via path traversal, potentially disrupting system operations.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 May 2023
- **Updated:** 29 Jan 2025
- **Also known as:** GHSA-wxvm-h7p9-98qp

## What is CVE-2023-31476?

CVE-2023-31476 is a high-severity path traversal vulnerability in n/a, published on 9 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered on GL.iNet devices running firmware before 3.216. There is an arbitrary file write in which an empty file can be created almost anywhere on the filesystem, as long as the filename and path is no more than 6 characters (the working directory is /www).

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

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

It affects 2 products.


Products: Gl-Inet Gl-Mv1000 Firmware, Gl-Inet Gl-Mv1000w Firmware.

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

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

## Is CVE-2023-31476 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-31476 is a high-severity path traversal vulnerability in n/a, published on 9 May 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-2023-31476 exists.

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-2023-31476/ (Markdown: https://insights.sbomify.com/CVE-2023-31476/index.md)
```

## Sources

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

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