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

> A weak PIN algorithm allows any user to bypass group policy restrictions and elevate to Administrator privileges in Admin By Request.

- **Severity:** High 8.2 (`CVSS:3.0/AC:L/AV:L/A:N/C:H/I:H/PR:N/S:C/UI:R`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 23 Jan 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-mxgh-5jc3-jf47

## What is CVE-2019-17202?

CVE-2019-17202 is a high-severity vulnerability in n/a, published on 23 Jan 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

FastTrack Admin By Request 6.1.0.0 supports group policies that are supposed to allow only a select range of users to elevate to Administrator privilege at will. If a user does not have direct access to the elevation feature through group policies, they are prompted to enter a PIN code in a challenge-response manner upon attempting to elevate privileges. The challenge's response uses a simple algorithm that can be easily emulated via data (customer ID and device name) available to all users, and thus any user can elevate to Administrator privilege.

Weakness: CWE-269 (Improper Privilege Management)

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

It affects 1 product.


Products: Fasttracksoftware Admin by Request.

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

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

## Is CVE-2019-17202 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-17201](https://insights.sbomify.com/CVE-2019-17201/): Missing authorization in n/a (critical 9.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-17202 is a high-severity vulnerability in n/a, published on 23 Jan 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-17202 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-17202/ (Markdown: https://insights.sbomify.com/CVE-2019-17202/index.md)
```

## Sources

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

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