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

> Low-privileged users can bypass authorization controls to perform administrative actions, leading to full system compromise.

- **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:** 19 Mar 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-7wx9-pg9m-2r55

## What is CVE-2019-16071?

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

### Official description

Enigma NMS 65.0.0 and prior allows administrative users to create low-privileged accounts that do not have the ability to modify any settings in the system, only view the components. However, it is possible for a low-privileged user to perform all actions as an administrator by bypassing authorization controls and sending requests to the server in the context of an administrator.

Weakness: CWE-269 (Improper Privilege Management)

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

It affects 1 product.


Products: Netsas Enigma Nms.

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

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

## Is CVE-2019-16071 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-16071 is a high-severity vulnerability in n/a, published on 19 Mar 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-16071 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-16071/ (Markdown: https://insights.sbomify.com/CVE-2019-16071/index.md)
```

## Sources

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

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