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

> Attackers can use static credentials to access the DIM interface on NEC PBX devices, potentially leading to unauthorized control.

- **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-pch4-wfwx-j685

## What is CVE-2019-20033?

CVE-2019-20033 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

On Aspire-derived NEC PBXes, including all versions of SV8100 devices, a set of documented, static login credentials may be used to access the DIM interface.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Nec Sv8100 Firmware.

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

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

## Is CVE-2019-20033 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-20033 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-20033 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-20033/ (Markdown: https://insights.sbomify.com/CVE-2019-20033/index.md)
```

## Sources

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

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