# CVE-2019-20030: Auth bypass in n/a

> An attacker knowing the modem access number can bypass authentication via SSH tunneling to access the LAN port of the NEC UM8000 voicemail system.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Jul 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-wxqp-g33r-6xx2

## What is CVE-2019-20030?

CVE-2019-20030 is a high-severity authentication bypass vulnerability in n/a, published on 29 Jul 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An attacker with knowledge of the modem access number on a NEC UM8000 voicemail system may use SSH tunneling or standard Linux utilities to gain access to the system's LAN port. All versions are affected.

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

It affects 1 product.


Products: Nec Um8000 Firmware.

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

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

## Is CVE-2019-20030 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-20030 is a high-severity authentication bypass vulnerability in n/a, published on 29 Jul 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-20030 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-20030/ (Markdown: https://insights.sbomify.com/CVE-2019-20030/index.md)
```

## Sources

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

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