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

> Remote attackers can read arbitrary files on Arris gateways due to a path traversal flaw in the muhttpd server.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Aug 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-c4c9-87fm-m8qc

## What is CVE-2022-31793?

CVE-2022-31793 is a high-severity path traversal vulnerability in n/a, published on 4 Aug 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

do_request in request.c in muhttpd before 1.1.7 allows remote attackers to read arbitrary files by constructing a URL with a single character before a desired path on the filesystem. This occurs because the code skips over the first character when serving files. Arris NVG443, NVG599, NVG589, and NVG510 devices and Arris-derived BGW210 and BGW320 devices are affected.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 7 products.


Products: Arris Bgw210 Firmware, Arris Bgw320 Firmware, Arris Nvg443 Firmware, Arris Nvg510 Firmware, Arris Nvg589 Firmware, Arris Nvg599 Firmware, Inglorion Muhttpd.

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

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

## Is CVE-2022-31793 being exploited?

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

Public exploit code:

- https://github.com/xpgdgit/CVE-2022-31793 (github_poc): https://github.com/xpgdgit/CVE-2022-31793
- muhttpd <=1.1.5 - Local Inclusion (nuclei)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-31793 is a high-severity path traversal vulnerability in n/a, published on 4 Aug 2022. 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-31793 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-2022-31793/ (Markdown: https://insights.sbomify.com/CVE-2022-31793/index.md)
```

## Sources

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

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