dbcve.org
Active Management Technology FirmwareOperating system · Intel

CVE-2019-11131

CRITICAL · 9.8 CVSS v3.1 Published 2019-12-18
Fix available
A fix is available. Upgrade to 11.8.70 / 11.11.70 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Logic issue in subsystem in Intel(R) AMT before versions 11.8.70, 11.11.70, 11.22.70 and 12.0.45 may allow an unauthenticated user to potentially enable escalation of privilege via 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

A logic vulnerability in Intel Active Management Technology (AMT) subsystem allows an unauthenticated remote attacker to escalate privileges via network access. The flaw exists in versions before 11.8.70, 11.11.70, 11.22.70, and 12.0.45, enabling potential complete system compromise without authentication.

MitigationUpdate Intel AMT firmware to version 11.8.70, 11.11.70, 11.22.70, 12.0.45 or later. If patching is not immediately feasible, disable AMT or restrict network access to management interfaces.

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.0, < 11.8.70>= 11.10, < 11.11.70>= 11.20, < 11.22.70>= 12.0, < 12.0.45

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

CVSS:3.1/AV:N/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 checks

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

  1. Confirm Intel AMT is provisioned and enabled
    Access the Intel Management Engine BIOS Extension (MEBx) during system boot, or check via Intel AMT configuration tools or the web interface on ports 16992/16993
    Affected if AMT is enabled and provisioned - the vulnerability only affects systems with AMT active
  2. Determine the Intel AMT firmware version
    Retrieve the AMT firmware version via MEBx, Intel SCS configuration software, the AMT web interface, or the Intel AMT SDK. Common access points include the 'General Settings' or ' firmware version' display in the management interface
    Affected if The installed version falls within any of these ranges: >= 11.0 and < 11.8.70, OR >= 11.10 and < 11.11.70, OR >= 11.20 and < 11.22.70, OR >= 12.0 and < 12.0.45
  3. Verify AMT network accessibility
    Check if ports 16992 (HTTP) or 16993 (HTTPS) used by Intel AMT are exposed on the network. Scan local network interfaces or review firewall rules for inbound access to these ports
    Affected if The AMT management ports are reachable from untrusted network segments - this is required for remote exploitation

A system is affected if Intel AMT is enabled and the firmware version is less than 11.8.70, 11.11.70, 11.22.70, or 12.0.45 (depending on the major version branch), with AMT network interfaces exposed.

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.

dbcve · scoped
Upgrade available Upgrade to 11.8.70 / 11.11.70 / 11.22.70 or later
Fixed in 11.8.7011.11.7011.22.70
Interim mitigation

Update Intel AMT firmware to version 11.8.70, 11.11.70, 11.22.70, 12.0.45 or later. If patching is not immediately feasible, disable AMT or restrict network access to management interfaces.

Recommended fix High confidence

Upgrade to version 11.8.70 (for 11.x branches), 11.11.70 (for 11.10 branch), 11.22.70 (for 11.20 branch), or 12.0.45 (for 12.x branch)

  1. Identify the current Intel AMT firmware version by accessing the Intel AMT web interface or using the amtversion command via local WS-Management
  2. Navigate to the Intel Support website and download the appropriate Intel AMT firmware update for your specific version branch
  3. Apply the firmware update using Intel Management Engine Interface (MEI) or through the Intel AMT web interface in 'Admin' mode
  4. Restart the system after the firmware update completes
  5. Verify the installed firmware version matches the target fixed version (minimum 11.8.70, 11.11.70, 11.22.70, or 12.0.45 depending on your version branch)
Caveat Firmware updates may require system downtime and could reset AMT configuration to defaults; backup configuration before updating

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Active Management Technology Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation10.0 h
  • Testing5.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,510
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-11131 — 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-11131 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