CVE-2019-11087
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 input validation in the subsystem for Intel(R) CSME before versions 11.8.70, 11.11.70, 11.22.70, 12.0.45, 13.0.10 and 14.0.10; Intel(R) TXE before versions 3.1.70 and 4.0.20 may allow a privileged user to potentially enable escalation of privilege, information disclosure or denial of service 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 · high confidenceInsufficient input validation in Intel CSME and TXE firmware allows a privileged local user to potentially escalate privileges, disclose information, or cause denial of service. This is a firmware-level vulnerability affecting low-level security subsystems on Intel processors.
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 data>= 11.0, < 11.8.70>= 11.10, < 11.11.70>= 11.20, < 11.22.70>= 12.0, < 12.0.45>= 13.0, < 13.0.10>= 14.0.0, < 14.0.10>= 3.0, < 3.1.70>= 4.0, < 4.0.20CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
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.
-
Verify system has Intel CSME or TXE firmwareCheck system information or Intel utility for the presence of Intel Management Engine (ME) or Trusted Execution Engine (TXE). On Windows, run 'wmic baseboard get product,manufacturer' or use Intel System Information Utility.Affected if System does not contain Intel CSME or TXE firmware (not applicable)
-
Retrieve Intel CSME firmware versionUse Intel System Information Utility (Intel SIU), Intel Management Engine Interface (MEI) driver with 'wmic /namespace:\\root\wmi PATH MSME_DRV get /all' or check BIOS/UEFI setup screen under 'Advanced' or 'Security' menu for 'Intel Management Engine' version.Affected if Installed CSME version matches any of these vulnerable ranges: 11.0-11.8.69, 11.10-11.11.69, 11.20-11.22.69, 12.0-12.0.44, 13.0-13.0.9, or 14.0.0-14.0.9
-
Retrieve Intel TXE firmware versionUse Intel System Information Utility, Intel TXE driver information, or check BIOS/UEFI setup screen under 'Advanced' or 'Security' menu for 'Intel Trusted Execution Engine' version.Affected if Installed TXE version matches any of these vulnerable ranges: 3.0-3.1.69 or 4.0-4.0.19
System is affected if it contains Intel CSME firmware versions 11.x prior to 11.8.70/11.11.70/11.22.70, 12.x prior to 12.0.45, 13.x prior to 13.0.10, or 14.x prior to 14.0.10; or Intel TXE firmware versions 3.x prior to 3.1.70 or 4.x prior to 4.0.20.
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 data3.1.704.0.2011.8.70
Update Intel CSME firmware to versions 11.8.70+, 11.11.70+, 11.22.70+, 12.0.45+, 13.0.10+, or 14.0.10+ and Intel TXE to 3.1.70+ or 4.0.20+ as appropriate for the hardware platform.
- 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-11087 — 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-11087 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