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

> Hardcoded root password in Zhuhai RaySharp firmware allows remote attackers to gain unauthorized access via Telnet or custom ports.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Feb 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-46p6-93mm-3qxw

## What is CVE-2015-8286?

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

### Official description

Zhuhai RaySharp firmware has a hardcoded root password, which makes it easier for remote attackers to obtain access via a session on TCP port 23 or 9000.

Weakness: CWE-254

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

It affects 1 product.


Products: Zhuhai Raysharp Firmware.

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

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

## Is CVE-2015-8286 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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