CVE-2019-11086
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 subsystem for Intel(R) AMT before version 12.0.45 may allow an unauthenticated user to potentially enable escalation of privilege via physical 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 the Intel Active Management Technology (AMT) subsystem before version 12.0.45 allows an unauthenticated user with physical access to potentially escalate privileges. This is a firmware-level vulnerability in Intel's out-of-band management technology that could allow an attacker with direct physical access to the affected system to gain elevated credentials.
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>= 12.0, < 12.0.45CVSS 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
- Physical
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:P/AC:L/PR:N/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.
-
Determine if Intel AMT is present and enabledAccess the system BIOS/UEFI settings during boot and look for Intel AMT, Intel vPro, or Intel Management Engine configuration options. Alternatively, on Windows use Device Manager to check for Intel Management Engine Interface under System devices. On Linux, check for the mei kernel module or look in /sys/class/mei/Affected if Intel AMT is enabled and present on the system; if AMT is disabled or not available, this vulnerability does not apply
-
Compare your firmware version against the vulnerable rangeThe detected AMT firmware version must be >= 12.0 but < 12.0.45 to be affected by CVE-2019-11086. Versions below 12.0 or 12.0.45 and later are not vulnerable to this specific issueAffected if Your installed Intel AMT firmware version is 12.0.x where x is any version less than 45, or specifically any version from 12.0 through 12.0.44
You are affected if Intel AMT is enabled on your system AND the installed AMT firmware version falls within 12.0 to 12.0.44 inclusive; systems without AMT or with version 12.0.45 or later are not affected by this CVE.
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 data12.0.45
Update Intel AMT firmware to version 12.0.45 or later. This typically requires updating the system BIOS/UEFI and Intel AMT firmware through vendor management tools or enterprise deployment infrastructure.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.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 $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-11086 — 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-11086 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