# CVE-2019-20025: Hardcoded credentials in n/a

> Unauthenticated attackers can log in with hardcoded manufacturer credentials to gain full control of NEC SV9100 PBX devices.

- **Severity:** Critical 9.8 (`CVSS:3.1/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:** 29 Jul 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-7q4r-vh4x-gr7v

## What is CVE-2019-20025?

CVE-2019-20025 is a critical vulnerability in n/a, published on 29 Jul 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Certain builds of NEC SV9100 software could allow an unauthenticated, remote attacker to log into a device running an affected release with a hardcoded username and password, aka a Static Credential Vulnerability. The vulnerability is due to an undocumented user account with manufacturer privilege level. An attacker could exploit this vulnerability by using this account to remotely log into an affected device. A successful exploit could allow the attacker to log into the device with manufacturer level access. This vulnerability affects SV9100 PBXes that are running software release 6.0 or higher. This vulnerability does not affect SV9100 software releases prior to 6.0.

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

## Which versions are affected by CVE-2019-20025?

It affects 1 product.


Products: Nec Sv9100 Firmware.

## How do I fix CVE-2019-20025?

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

## Is CVE-2019-20025 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-20026](https://insights.sbomify.com/CVE-2019-20026/): Auth bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-20025 and fix it if it is affected.

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

## Sources

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

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