# CVE-2021-44899: Privilege escalation in n/a

> Attackers can escalate privileges by sending specific IOCTL requests to vulnerable drivers in MSI Center.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Feb 2022
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-fh39-3mgf-f647

## What is CVE-2021-44899?

CVE-2021-44899 is a high-severity vulnerability in n/a, published on 4 Feb 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Micro-Star International (MSI) Center <= 1.0.31.0 is vulnerable to multiple Privilege Escalation vulnerabilities in the atidgllk.sys, atillk64.sys, MODAPI.sys, NTIOLib.sys, NTIOLib_X64.sys, WinRing0.sys, WinRing0x64.sys drivers components. All the vulnerabilities are triggered by sending specific IOCTL requests.

## Which versions are affected by CVE-2021-44899?

It affects 1 product.


Products: Msi Center.

## How do I fix CVE-2021-44899?

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

## Is CVE-2021-44899 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-31877](https://insights.sbomify.com/CVE-2022-31877/): Privilege escalation in n/a (high 8.8)
- [CVE-2022-38532](https://insights.sbomify.com/CVE-2022-38532/): Privilege escalation in n/a (high 7.8)
- [CVE-2026-37453](https://insights.sbomify.com/CVE-2026-37453/): Information disclosure in n/a (high 7.5)
- [CVE-2026-37454](https://insights.sbomify.com/CVE-2026-37454/): Information disclosure in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-44899 and fix it if it is affected.

What it is: CVE-2021-44899 is a high-severity vulnerability in n/a, published on 4 Feb 2022. 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-2021-44899 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-2021-44899/ (Markdown: https://insights.sbomify.com/CVE-2021-44899/index.md)
```

## Sources

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

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