CVE-2019-0184
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedInsufficient access control in protected memory subsystem for Intel(R) TXT for 6th, 7th, 8th and 9th Generation Intel(R) Core(TM) Processor Families; Intel(R) Xeon(R) Processor E3-1500 v5 and v6 Families; Intel(R) Xeon(R) E-2100 and E-2200 Processor Families with Intel(R) Processor Graphics and Intel(R) TXT may allow a privileged user to potentially enable information disclosure via local access.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceInsufficient access control in Intel TXT (Trusted Execution Technology) protected memory subsystem allows a privileged local user to potentially enable information disclosure. This affects specific generations of Intel Core and Xeon processors with Intel Processor Graphics and Intel TXT.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify your processor modelRun 'wmic cpu get name' on Windows or 'cat /proc/cpuinfo' on Linux to find the exact CPU modelAffected if The CPU model matches one of these: Intel Core I7 8700b, I7 8850h, I9 9880h, I7 9850h, I5 9400h, I7 8700, I7 8700k, or I7 8700t
-
Verify Intel TXT is enabledCheck BIOS/UEFI settings for Intel TXT (Trusted Execution Technology) or TXT option, or use the 'txt-stat' command on Linux if availableAffected if Intel TXT is currently enabled in the system firmware settings
-
Check TXT software stack statusOn Linux, run 'ls /sys/kernel/security/txt' or check if the TPM/TXT modules are loaded via 'lsmod | grep -i txt'Affected if Intel TXT is actively initialized and running on the system
-
Review firmware/microcode versionCheck BIOS/UEFI version information displayed at system boot or via 'dmidecode -s bios-version' on Linux; check microcode via 'cat /proc/cpuinfo' looking for microcode versionAffected if The installed firmware or microcode version predates any available Intel security update for this CVE (Intel has not specified fixed versions for these affected models)
Your system is affected if you run any of the listed Intel Core processor models (8700b, 8850h, 9880h, 9850h, 9400h, 8700, 8700k, 8700t) and have Intel TXT enabled in your BIOS/UEFI settings.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply Intel firmware/microcode updates and BIOS/UEFI updates provided by Intel for the affected processor families. Verify Intel TXT functionality after patching.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-0184 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-0184 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data