# CVE-2015-7856: Hardcoded credentials in n/a

> Remote attackers can gain unauthorized access to OpenNMS using the default rtc account credentials.

- **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:** 16 Oct 2015
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-469j-c2x8-3w38

## What is CVE-2015-7856?

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

### Official description

OpenNMS has a default password of rtc for the rtc account, which makes it easier for remote attackers to obtain access by leveraging knowledge of the credentials.

Weakness: CWE-255

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

It affects 1 product.


Products: Opennms Opennms.

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

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

## Is CVE-2015-7856 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-6555](https://insights.sbomify.com/CVE-2016-6555/): OpenNMS Stored XSS via SNMP Trap Alerts (high 7.1)
- [CVE-2016-6556](https://insights.sbomify.com/CVE-2016-6556/): OpenNMS Stored XSS via SNMP Agent Data (high 7.1)
- [CVE-2020-1652](https://insights.sbomify.com/CVE-2020-1652/): Junos Space: OpenNMS is accessible via port 9443 (medium 5.6)
- [CVE-2014-3960](https://insights.sbomify.com/CVE-2014-3960/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2008-6095](https://insights.sbomify.com/CVE-2008-6095/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

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

## Sources

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

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