# CVE-2019-1010066: Privilege escalation in msr-safe

> An attacker can bypass access controls to modify model specific registers, potentially escalating privileges or executing code.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Jul 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-jfjq-mr93-rm2h

## What is CVE-2019-1010066?

CVE-2019-1010066 is a high-severity vulnerability in Lawrence Livermore National Laboratory msr-safe, published on 18 Jul 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Lawrence Livermore National Laboratory msr-safe v1.1.0 is affected by: Incorrect Access Control. The impact is: An attacker could modify model specific registers. The component is: ioctl handling. The attack vector is: An attacker could exploit a bug in ioctl interface whitelist checking, in order to write to model specific registers, normally a function reserved for the root user. The fixed version is: v1.2.0.

Weakness: CWE-862 (Missing Authorization), CWE-269 (Improper Privilege Management)

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

It affects 1 product.


Products: Llnl Model Specific Registers-Safe.

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

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

## Is CVE-2019-1010066 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-1010066 is a high-severity vulnerability in Lawrence Livermore National Laboratory msr-safe, published on 18 Jul 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-1010066 in the wild and no public exploit code.

Affected product: Lawrence Livermore National Laboratory msr-safe. 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-1010066/ (Markdown: https://insights.sbomify.com/CVE-2019-1010066/index.md)
```

## Sources

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

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