# CVE-2015-2284: Privilege escalation in n/a

> Remote attackers can escalate privileges and execute arbitrary code in SolarWinds Firewall Security Manager via client session handling flaws.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Mar 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-f4c8-vf94-3wc7

## What is CVE-2015-2284?

CVE-2015-2284 is a critical vulnerability in n/a, published on 24 Mar 2015. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

userlogin.jsp in SolarWinds Firewall Security Manager (FSM) before 6.6.5 HotFix1 allows remote attackers to gain privileges and execute arbitrary code via unspecified vectors, related to client session handling.

Weakness: CWE-264

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

It affects 1 product.


Products: Solarwinds Firewall Security Manager.

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

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

## Is CVE-2015-2284 being exploited?

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

Public exploit code:

- Solarwinds Firewall Security Manager 6.6.5 Client Session Handling Vulnerability (metasploit)
- SolarWinds Firewall Security Manager 6.6.5 - Client Session Handling (Metasploit) (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2015-2284 is a critical vulnerability in n/a, published on 24 Mar 2015. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2015-2284 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-2284/ (Markdown: https://insights.sbomify.com/CVE-2015-2284/index.md)
```

## Sources

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

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