# CVE-2020-7819: nTracker USB Enterprise SQL-Injection vulnerability

> Remote unauthenticated attackers can exploit SQL injection to access sensitive user credentials and session data in nTracker USB Enterprise.

- **Severity:** Critical 9.3 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Sep 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-mvjq-qw5h-9cj2

## What is CVE-2020-7819?

CVE-2020-7819 is a critical SQL injection vulnerability in nTrackSystem nTracker USB Enterprise, published on 7 Sep 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A SQL-Injection vulnerability in the nTracker USB Enterprise(secure USB management solution) allows a remote unauthenticated attacker to perform SQL query to access username password and other session related information.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2020-7819?

It affects 1 product.


Products: Ntracker Ntracker Usb Enterprise.

## How do I fix CVE-2020-7819?

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

## Is CVE-2020-7819 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-7819 and fix it if it is affected.

What it is: CVE-2020-7819 is a critical SQL injection vulnerability in nTrackSystem nTracker USB Enterprise, published on 7 Sep 2021. 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-2020-7819 in the wild and no public exploit code.

Affected product: nTrackSystem nTracker USB Enterprise. 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-2020-7819/ (Markdown: https://insights.sbomify.com/CVE-2020-7819/index.md)
```

## Sources

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

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