# CVE-2019-20029: Privilege escalation in n/a

> Attackers can escalate privileges to developer level on NEC PBX devices via a crafted HTTP POST request.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Jul 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-xvv3-3j3q-vgxg

## What is CVE-2019-20029?

CVE-2019-20029 is a high-severity vulnerability in n/a, published on 29 Jul 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An exploitable privilege escalation vulnerability exists in the WebPro functionality of Aspire-derived NEC PBXes, including all versions of SV8100, SV9100, SL1100 and SL2100 devices. A specially crafted HTTP POST can cause privilege escalation resulting in a higher privileged account, including an undocumented developer level of access.

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

It affects 4 products.


Products: Nec Sl1100 Firmware, Nec Sl2100 Firmware, Nec Sv8100 Firmware, Nec Sv9100 Firmware.

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

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

## Is CVE-2019-20029 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-20027](https://insights.sbomify.com/CVE-2019-20027/): Auth bypass in n/a (critical 9.8)
- [CVE-2019-20028](https://insights.sbomify.com/CVE-2019-20028/): Missing authorization in n/a (high 7.5)
- [CVE-2019-20032](https://insights.sbomify.com/CVE-2019-20032/): Auth bypass in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-20029 is a high-severity vulnerability in n/a, published on 29 Jul 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-20029 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-20029/ (Markdown: https://insights.sbomify.com/CVE-2019-20029/index.md)
```

## Sources

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

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