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

> Hardcoded SSH keys in Advantech industrial gateways allow remote attackers to gain unauthorized access without authentication.

- **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:** 7 Nov 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-c77h-w7c8-63x2

## What is CVE-2015-6476?

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

### Official description

Advantech EKI-122x-BE devices with firmware before 1.65, EKI-132x devices with firmware before 1.98, and EKI-136x devices with firmware before 1.27 have hardcoded SSH keys, which makes it easier for remote attackers to obtain access via an SSH session.

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

It affects 5 products.


Products: Advantech Eki-122x Series Firmware, Advantech Eki-1321 Series Firmware, Advantech Eki-1322 Series Firmware, Advantech Eki-1361 Series Firmware, Advantech Eki-1362 Series Firmware.

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

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

## Is CVE-2015-6476 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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