# CVE-2020-15313: Hardcoded credentials in n/a

> Attackers can use a hardcoded ECDSA SSH key to gain root access to Zyxel CloudCNM SecuManager devices.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/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:** 29 Jun 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-vw7q-vwxc-j4q4

## What is CVE-2020-15313?

CVE-2020-15313 is a medium-severity vulnerability in n/a, published on 29 Jun 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Zyxel CloudCNM SecuManager 3.1.0 and 3.1.1 has a hardcoded ECDSA SSH key for the root account.

Weakness: CWE-798 (Use of Hard-coded Credentials)

## Which versions are affected by CVE-2020-15313?

It affects 1 product.


Products: Zyxel Cloudcnm Secumanager.

## How do I fix CVE-2020-15313?

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

## Is CVE-2020-15313 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-15320](https://insights.sbomify.com/CVE-2020-15320/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2020-15321](https://insights.sbomify.com/CVE-2020-15321/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2020-15322](https://insights.sbomify.com/CVE-2020-15322/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2020-15323](https://insights.sbomify.com/CVE-2020-15323/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2020-15331](https://insights.sbomify.com/CVE-2020-15331/): Hardcoded credentials in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-15313 and fix it if it is affected.

What it is: CVE-2020-15313 is a medium-severity vulnerability in n/a, published on 29 Jun 2020. 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-2020-15313 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-2020-15313/ (Markdown: https://insights.sbomify.com/CVE-2020-15313/index.md)
```

## Sources

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

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