dbcve.org
Active Management Technology FirmwareOperating system · Intel

CVE-2019-0096

HIGH · 8.0 CVSS v3.1 Published 2019-05-17
Fix available
A fix is available. Upgrade to 11.8.65 / 11.11.65 or later.
See remediation →
82/100
Remediation priority · High
Zero-click

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 · unedited
Out of bound write vulnerability in subsystem for Intel(R) AMT before versions 11.8.65, 11.11.65, 11.22.65, 12.0.35 may allow an authenticated user to potentially enable escalation of privilege via adjacent network 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 confidence

Out-of-bounds write vulnerability in Intel Active Management Technology (AMT) subsystem allows an authenticated user to write beyond allocated memory boundaries. Successful exploitation enables privilege escalation. The attack requires adjacent network access to the AMT interface.

MitigationUpdate Intel AMT to version 11.8.65, 11.11.65, 11.22.65, 12.0.35 or later. Until patched, limit network accessibility of AMT interfaces to prevent adjacent network attackers.

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
Active Management Technology FirmwareOperating system
Affected:>= 11.8.0, < 11.8.65>= 11.11.0, < 11.11.65>= 11.22.0, < 11.22.65>= 12.0, < 12.0.35

CVSS 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
Adjacent
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Intel AMT hardware is present
    Check system specifications for Intel vPro capability, or inspect the BIOS/UEFI for Intel Active Management Technology options. On Linux, list MEI devices with `ls -la /sys/class/mei/` or check `dmesg | grep mei` for Management Engine interface detection.
    Affected if No MEI devices found and no AMT option in BIOS indicates the system is not vulnerable to this specific AMT flaw.
  2. Verify AMT firmware is provisioned and enabled
    Access the AMT configuration via BIOS/UEFI settings (typically under "Intel AMT" or "Active Management Technology"), or use Intel Management Engine interface tools to confirm AMT state.
    Affected if If AMT is disabled or not provisioned, the vulnerability cannot be exploited even if the firmware version is affected.
  3. Retrieve the installed AMT firmware version
    Access the AMT web interface via https://localhost:16992 or https://16993 (if enabled), or use Intel AMT SDK/Windows: `wmic /namespace:\\root\Intel\ME PATH Intel_AMTInstance GET Version`. Check BIOS revision information under "Intel ME" or "Management Engine" firmware version.
    Affected if The specific firmware version number is required to determine if it falls within affected ranges.
  4. Compare installed version against affected ranges
    Review the retrieved version against these affected ranges: 11.8.0 to 11.8.64, 11.11.0 to 11.11.64, 11.22.0 to 11.22.64, or 12.0 to 12.0.34. Versions at or above the upper bound (11.8.65, 11.11.65, 11.22.65, 12.0.35) are patched.
    Affected if The installed version falls within any of the four affected ranges listed, the system is vulnerable to the out-of-bounds write flaw.
  5. Assess network exposure of AMT interface
    Determine if AMT network ports (16992/16993) are accessible from the network. Check firewall rules, VLAN segmentation, and whether AMT is bound to dedicated or shared network interfaces.
    Affected if The vulnerability requires adjacent network access to the AMT interface; if AMT is isolated or inaccessible from network segments, exploitation risk is significantly reduced regardless of version.

A system is affected if it has Intel AMT enabled with firmware version falling within any of the four vulnerable ranges AND the AMT interface is network-accessible to adjacent attackers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 11.8.65 / 11.11.65 / 11.22.65 or later
Fixed in 11.8.6511.11.6511.22.65
Interim mitigation

Update Intel AMT to version 11.8.65, 11.11.65, 11.22.65, 12.0.35 or later. Until patched, limit network accessibility of AMT interfaces to prevent adjacent network attackers.

Fix this in Active Management Technology Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-0096 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-0096 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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