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

> Attackers can read arbitrary files on Linksys MR9600 routers by exploiting symbolic links in NAS SMB shares.

- **Severity:** Medium 4.6 (`CVSS:3.1/AV:P/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Apr 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-2vfm-65cj-5j48

## What is CVE-2022-24372?

CVE-2022-24372 is a medium-severity path traversal vulnerability in n/a, published on 27 Apr 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Linksys MR9600 devices before 2.0.5 allow attackers to read arbitrary files via a symbolic link to the root directory of a NAS SMB share.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

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

It affects 1 product.


Products: Linksys Mr9600 Firmware.

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

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

## Is CVE-2022-24372 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2026-4558](https://insights.sbomify.com/CVE-2026-4558/): Linksys MR9600 SmartConnect.lua smartConnectConfigure os command injection (high 8.7)
- [CVE-2026-6992](https://insights.sbomify.com/CVE-2026-6992/): Linksys MR9600 JNAP Action run_central2.sh BTRequestGetSmartConnectStatus os command injection (high 8.6)
- [CVE-2026-25603](https://insights.sbomify.com/CVE-2026-25603/): Path Traversal vulnerability in Linksys MR9600, Linksys MX4200 (medium 6.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-24372 is a medium-severity path traversal vulnerability in n/a, published on 27 Apr 2022. 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-2022-24372 in the wild and no public exploit code.

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

## Sources

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

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