# CVE-2019-0174: Information disclosure in Central Processing Units (CPUs)

> An authenticated local attacker can exploit a logic condition in Intel CPUs to disclose partial physical address information.

- **Severity:** Low 3.3 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/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:** 13 Jun 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-89vj-vcjr-x263

## What is CVE-2019-0174?

CVE-2019-0174 is a low-severity vulnerability in Central Processing Units (CPUs), published on 13 Jun 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Logic condition in specific microprocessors may allow an authenticated user to potentially enable partial physical address information disclosure via local access.

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

It affects 188 products.


Products: Intel 2000e Firmware, Intel 2002e Firmware, Intel 2950m Firmware, Intel 2955u Firmware, Intel 2957u Firmware, Intel 2961y Firmware, Intel 2970m Firmware, Intel 2980u Firmware, Intel 2981u Firmware, Intel 3550m Firmware, Intel 3556u Firmware, Intel 3558u Firmware, Intel 3560m Firmware, Intel 3560y Firmware, Intel 3561y Firmware, Intel 3805u Firmware, Intel 3825u Firmware, Intel E3-1220 Firmware, Intel E3-1220l Firmware, Intel E3-1225 Firmware and 168 more.

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

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

## Is CVE-2019-0174 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-0174 is a low-severity vulnerability in Central Processing Units (CPUs), published on 13 Jun 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-0174 in the wild and no public exploit code.

Affected product: Central Processing Units (CPUs). 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-0174/ (Markdown: https://insights.sbomify.com/CVE-2019-0174/index.md)
```

## Sources

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

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