# CVE-2015-1501: Code injection in n/a

> Remote attackers can execute arbitrary code in SolarWinds SAM by exploiting a code injection vulnerability in the graph editor control.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Feb 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-mcx9-5vc5-3pgf

## What is CVE-2015-1501?

CVE-2015-1501 is a medium-severity code injection vulnerability in n/a, published on 16 Feb 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The factory.loadExtensionFactory function in TSUnicodeGraphEditorControl in SolarWinds Server and Application Monitor (SAM) allow remote attackers to execute arbitrary code via a UNC path to a crafted binary.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2015-1501?

It affects 1 product.


Products: Solarwinds Server and Application Monitor.

## How do I fix CVE-2015-1501?

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

## Is CVE-2015-1501 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-47508](https://insights.sbomify.com/CVE-2022-47508/): Disable NTLM: SAM 2022.4 (high 7.5)
- [CVE-2015-1500](https://insights.sbomify.com/CVE-2015-1500/): Memory corruption in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-1501 and fix it if it is affected.

What it is: CVE-2015-1501 is a medium-severity code injection vulnerability in n/a, published on 16 Feb 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-1501 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-2015-1501/ (Markdown: https://insights.sbomify.com/CVE-2015-1501/index.md)
```

## Sources

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

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