# CVE-2019-6716: Missing authorization in n/a

> Unauthenticated attackers can enumerate Active Directory users and modify server jobs, potentially causing denial of service.

- **Severity:** Critical 9.4 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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:** 17 Mar 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-gx48-q3wg-hqgq

## What is CVE-2019-6716?

CVE-2019-6716 is a critical missing authorization vulnerability in n/a, published on 17 Mar 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An unauthenticated Insecure Direct Object Reference (IDOR) in Wicket Core in LogonBox Nervepoint Access Manager 2013 through 2017 allows a remote attacker to enumerate internal Active Directory usernames and group names, and alter back-end server jobs (backup and synchronization jobs), which could allow for the possibility of a Denial of Service attack via a modified jobId parameter in a runJob.html GET request.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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

It affects 1 product.


Products: Logonbox Nervepoint Access Manager.

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

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

## Is CVE-2019-6716 being exploited?

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

Public exploit code:

- LogonBox Limited / Hypersocket Nervepoint Access Manager - (Unauthenticated) Insecure Direct Object Reference (exploitdb)

## Fix prompt for AI coding agents

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

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

## Sources

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

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