# CVE-2015-5610: Information disclosure in n/a

> Remote authenticated users can obtain cleartext domain-administrator passwords by exploiting a shared decryption key in SolarWinds N-Able N-Central.

- **Severity:** Medium 4.0 (`AV:N/AC:L/Au:S/C:P/I:N/A:N`)
- **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:** 21 Jul 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-98wj-37r9-8cv3

## What is CVE-2015-5610?

CVE-2015-5610 is a medium-severity vulnerability in n/a, published on 21 Jul 2015. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The RSM (aka RSMWinService) service in SolarWinds N-Able N-Central before 9.5.1.4514 uses the same password decryption key across different customers' installations, which makes it easier for remote authenticated users to obtain the cleartext domain-administrator password by locating the encrypted password within HTML source code and then leveraging knowledge of this key from another installation.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Solarwinds N-Able N-Central.

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

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

## Is CVE-2015-5610 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2015-5610 is a medium-severity vulnerability in n/a, published on 21 Jul 2015. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-5610 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-5610/ (Markdown: https://insights.sbomify.com/CVE-2015-5610/index.md)
```

## Sources

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

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