# CVE-2019-0162: Information disclosure in Microprocessor Memory Mapping Advisory

> An authenticated local attacker can exploit virtual memory mapping flaws in Intel microprocessors to disclose sensitive information.

- **Severity:** Low 3.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N`)
- **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:** 17 Apr 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-2wvw-h8hc-x343

## What is CVE-2019-0162?

CVE-2019-0162 is a low-severity vulnerability in Microprocessor Memory Mapping Advisory, published on 17 Apr 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Memory access in virtual memory mapping for some microprocessors may allow an authenticated user to potentially enable information disclosure via local access.

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

It affects 1 product.


Products: Intel -.

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

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

## Is CVE-2019-0162 being exploited?

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

Public exploit code:

- Speculative Load Hazards Boost Rowhammer and Cache Attacks - CVE-2019-0162 -  (github_poc): https://github.com/saadislamm/SPOILER

## Fix prompt for AI coding agents

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

What it is: CVE-2019-0162 is a low-severity vulnerability in Microprocessor Memory Mapping Advisory, published on 17 Apr 2019. 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-2019-0162 in the wild and no public exploit code.

Affected product: Microprocessor Memory Mapping Advisory. 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-0162/ (Markdown: https://insights.sbomify.com/CVE-2019-0162/index.md)
```

## Sources

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

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