# CVE-2023-23842: SolarWinds Network Configuration Manager Directory Traversal Vulnerability

> Administrative users can exploit a directory traversal flaw in SolarWinds Network Configuration Manager to execute arbitrary commands.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Jul 2023
- **Updated:** 23 Oct 2024
- **Also known as:** GHSA-4rx2-pvmr-h2r3

## What is CVE-2023-23842?

CVE-2023-23842 is a high-severity path traversal vulnerability in SolarWinds Network Configuration Manager, published on 26 Jul 2023. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The SolarWinds Network Configuration Manager was susceptible to the Directory Traversal Vulnerability. This vulnerability allows users with administrative access to SolarWinds Web Console to execute arbitrary commands.

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

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

It affects 1 product.


Products: Solarwinds Network Configuration Monitor.

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

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

## Is CVE-2023-23842 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-23842 is a high-severity path traversal vulnerability in SolarWinds Network Configuration Manager, published on 26 Jul 2023. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-23842 in the wild and no public exploit code.

Affected product: SolarWinds Network Configuration Manager. 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-23842/ (Markdown: https://insights.sbomify.com/CVE-2023-23842/index.md)
```

## Sources

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

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