# CVE-2022-21818: Information disclosure in NVIDIA License System

> Authenticated users can access other users' credentials, leading to privilege escalation and limited confidentiality/integrity impact.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N`)
- **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:** 14 Feb 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-rrqp-268p-3cf3

## What is CVE-2022-21818?

CVE-2022-21818 is a medium-severity vulnerability in NVIDIA License System, published on 14 Feb 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

NVIDIA License System contains a vulnerability in the installation scripts for the DLS virtual appliance, where a user on a network after signing in to the portal can access other users’ credentials, allowing them to gain escalated privileges, resulting in limited impact to both confidentiality and integrity.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information)

## Which versions are affected by CVE-2022-21818?

It affects 1 product.


Products: Nvidia License System.

## How do I fix CVE-2022-21818?

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

## Is CVE-2022-21818 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-21818 and fix it if it is affected.

What it is: CVE-2022-21818 is a medium-severity vulnerability in NVIDIA License System, published on 14 Feb 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-21818 in the wild and no public exploit code.

Affected product: NVIDIA License System. 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-2022-21818/ (Markdown: https://insights.sbomify.com/CVE-2022-21818/index.md)
```

## Sources

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

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