# CVE-2015-5371: File upload in n/a

> Remote attackers can upload and execute arbitrary scripts in SolarWinds Storage Manager via the AuthenticationFilter class.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Jul 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-4whj-xh57-pv6v

## What is CVE-2015-5371?

CVE-2015-5371 is a critical vulnerability in n/a, published on 6 Jul 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The AuthenticationFilter class in SolarWinds Storage Manager allows remote attackers to upload and execute arbitrary scripts via unspecified vectors.

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

It affects 1 product.


Products: Solarwinds Storage Manager.

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

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

## Is CVE-2015-5371 being exploited?

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

Public exploit code:

- SolarWinds Storage Manager Authentication Bypass (metasploit)

## Other vulnerabilities in n/a

- [CVE-2015-7838](https://insights.sbomify.com/CVE-2015-7838/): File upload in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2015-5371 is a critical vulnerability in n/a, published on 6 Jul 2015. 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-2015-5371 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-2015-5371/ (Markdown: https://insights.sbomify.com/CVE-2015-5371/index.md)
```

## Sources

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

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