CVE-2019-0092
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 vulnerability in subsystem for Intel(R) AMT before versions 11.8.65, 11.11.65, 11.22.65, 12.0.35 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 Intel AMT (Active Management Technology) subsystem allows an unauthenticated user with physical access to potentially escalate privileges. This is a firmware-level vulnerability in the out-of-band management component present on Intel-based systems.
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.8.0, < 11.8.65>= 11.11.0, < 11.11.65>= 11.22.0, < 11.22.65>= 12.0, < 12.0.35CVSS 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.
-
Check if Intel AMT is enabled on the systemAccess the system BIOS or UEFI settings and look for Intel AMT or Active Management Technology configuration options. On Windows, you can also use the Intel Management Engine Interface (MEI) driver and tools like 'Intel ME System Tools' to query AMT status.Affected if Intel AMT is enabled and present on the system
-
Retrieve the Intel AMT firmware versionAccess the Intel AMT web interface (typically accessible via https://localhost:16992 when AMT is enabled), use Intel's firmware version tools, or check via the Intel Management Engine BIOS extension (MEBX) accessible during system boot.Affected if The AMT firmware version cannot be determined or the system lacks AMT firmware support
-
Compare installed version against affected rangesMatch the retrieved AMT firmware version to these vulnerable ranges: 11.8.0 through 11.8.64, 11.11.0 through 11.11.64, 11.22.0 through 11.22.64, or 12.0 through 12.0.34. Any version matching these ranges indicates the system is affected.Affected if The installed AMT firmware version falls within any of the listed vulnerable version ranges
A system is affected if Intel AMT is enabled and the installed firmware version is one of the vulnerable versions listed in the affected ranges.
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 data11.8.6511.11.6511.22.65
Upgrade Intel AMT firmware to version 11.8.65, 11.11.65, 11.22.65, 12.0.35 or later. Physical access to the machine is required for exploitation, reducing remote risk but still requiring patching for defense-in-depth.
- Consultation4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-0092 — 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-0092 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