# CVE-2016-1561: Hardcoded credentials in n/a

> Remote attackers can gain root SSH access to ExaGrid appliances using a hardcoded private key, leading to full system compromise.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Apr 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-cwr4-jwc3-f83j

## What is CVE-2016-1561?

CVE-2016-1561 is a high-severity vulnerability in n/a, published on 21 Apr 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ExaGrid appliances with firmware before 4.8 P26 have a default SSH public key in the authorized_keys file for root, which allows remote attackers to obtain SSH access by leveraging knowledge of a private key from another installation or a firmware image.

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

## Which versions are affected by CVE-2016-1561?

It affects 8 products.


Products: Exagrid Ex10000e Firmware, Exagrid Ex13000e Firmware, Exagrid Ex21000e Firmware, Exagrid Ex3000 Firmware, Exagrid Ex32000e Firmware, Exagrid Ex40000e Firmware, Exagrid Ex5000 Firmware, Exagrid Ex7000 Firmware.

## How do I fix CVE-2016-1561?

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

## Is CVE-2016-1561 being exploited?

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

Public exploit code:

- ExaGrid - Known SSH Key and Default Password (Metasploit) (exploitdb)
- ExaGrid Known SSH Key and Default Password (metasploit)

## Other vulnerabilities in n/a

- [CVE-2016-1560](https://insights.sbomify.com/CVE-2016-1560/): Hardcoded credentials in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-1561 and fix it if it is affected.

What it is: CVE-2016-1561 is a high-severity vulnerability in n/a, published on 21 Apr 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2016-1561 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-2016-1561/ (Markdown: https://insights.sbomify.com/CVE-2016-1561/index.md)
```

## Sources

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

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