dbcve.org
Active Management Technology FirmwareOperating system · Intel

CVE-2019-11132

HIGH · 8.4 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 →
88/100
Remediation priority · High
Remotely reachable

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
Cross site scripting in subsystem in Intel(R) AMT before versions 11.8.70, 11.11.70, 11.22.70 and 12.0.45 may allow a privileged 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

Cross-site scripting (XSS) vulnerability in Intel Active Management Technology (AMT) subsystem. A privileged user with network access could inject malicious scripts that execute within the AMT web interface, potentially leading to escalation of privilege by hijacking administrative sessions or performing unauthorized actions.

MitigationUpgrade Intel AMT firmware to version 11.8.70, 11.11.70, 11.22.70, 12.0.45 or later. For systems where direct AMT update is not possible, consider disabling AMT or restricting network access to the AMT web interface via firewall rules.

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
High
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/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. Verify Intel AMT is present and enabled
    Access the system BIOS/UEFI settings and look for Intel AMT (Active Management Technology) or Intel vPro settings under the Advanced or Security tabs. Alternatively, on Windows, open Command Prompt and run 'wmic /namespace:\\root\cimv2\IntelMA get /value' or check Device Manager for 'Intel AMT' under System devices.
    Affected if Intel AMT is enabled in BIOS/UEFI and the firmware version falls within the affected ranges below.
  2. Determine the Intel AMT firmware version
    Access the AMT web interface by browsing to https://<hostname>:16992 or https://<hostname>:16993 (the default Intel AMT ports). Log in as an administrator and navigate to the 'Firmware Version' or 'General Settings' page. Alternatively, use the Intel Management Engine Interface (MEI) tool: 'wmic /namespace:\\root\cimv2\IntelMA path Intel_AMT_Firmware GET Version' or 'IntelMACS64.exe -meinfo' from the Intel Management Engine firmware tools.
    Affected if The firmware version displayed is one of the following: 11.x before 11.8.70, 11.10.x before 11.11.70, 11.20.x before 11.22.70, or 12.0.x before 12.0.45.
  3. Confirm AMT web interface is accessible
    Attempt to reach the AMT web interface by navigating to https://<system_ip>:16992 or https://<system_ip>:16993 from a browser. A successful connection displays the Intel AMT login page.
    Affected if The AMT web interface is reachable and responds with the Intel AMT login page, meaning the XSS payload could be injected.
  4. Compare installed version to affected ranges
    Match the identified firmware version against the affected ranges: >= 11.0 and < 11.8.70; >= 11.10 and < 11.11.70; >= 11.20 and < 11.22.70; >= 12.0 and < 12.0.45.
    Affected if The installed version falls within any of these ranges AND the AMT web interface is accessible on the network.

The environment is affected if Intel AMT is enabled, the web interface is network-accessible, and the firmware version is within any of the four vulnerable ranges listed.

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.70 / 11.11.70 / 11.22.70 or later
Fixed in 11.8.7011.11.7011.22.70
Interim mitigation

Upgrade Intel AMT firmware to version 11.8.70, 11.11.70, 11.22.70, 12.0.45 or later. For systems where direct AMT update is not possible, consider disabling AMT or restricting network access to the AMT web interface via firewall rules.

Fix this in Active Management Technology Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
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,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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