dbcve.org
Active Management Technology FirmwareOperating system · Intel

CVE-2018-12187

HIGH · 7.5 CVSS v3.0 Published 2019-03-14
Fix available
A fix is available. Upgrade to 11.8.60 / 11.11.60 or later.
See remediation →
84/100
Remediation priority · High
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
Insufficient input validation in Intel(R) Active Management Technology (Intel(R) AMT) before version 11.8.60, 11.11.60, 11.22.60 or 12.0.20 may allow an unauthenticated user to potentially cause a denial of service 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

Insufficient input validation in Intel Active Management Technology (Intel AMT) allows unauthenticated network attackers to cause denial of service. The vulnerability exists in the firmware-level management component present on vPro-enabled systems, where improper validation of network input can be exploited without authentication.

MitigationUpdate Intel AMT firmware to version 11.8.60, 11.11.60, 11.22.60, or 12.0.20 or later to remediate this vulnerability. If AMT is not required, consider disabling it to reduce the attack surface.

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.60>= 11.10, < 11.11.60>= 11.20, < 11.22.60>= 12.0.0, < 12.0.20

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
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 on the system
    Check if the system is vPro-enabled or inspect the Intel Management Engine (ME) interface using the 'mei-me' or 'mei' driver on Linux, or check Device Manager on Windows under 'System devices' for Intel Management Engine Interface. Alternatively, access the system BIOS/UEFI setup and look for Intel AMT or Intel vPro settings under 'Advanced' or 'Security' tabs.
    Affected if Intel AMT is not present or the Management Engine interface is not detected, the system is likely not affected by this vulnerability.
  2. Determine if Intel AMT is enabled
    On Windows, check if the Intel AMT service (Intel AMT Service, host-based service, or similar) is running via Services.msc, or verify in the BIOS/UEFI that AMT is provisioned or enabled. On Linux, check the status of the 'mei' or 'mei-me' modules with 'lsmod | grep mei' and look for AMT-related processes.
    Affected if If AMT is physically present on the chipset but completely disabled and unprovisioned, exploitation may not be possible, though the firmware version should still be checked.
  3. Obtain the Intel AMT firmware version
    Use Intel's MEInfo, Intel Management and Security Status, or Intel AMT Scupertest tool. On Windows, run 'MEInfoWin.exe -verbose' or use the Intel AMT SDK. On Linux, run 'meinfo' or 'meiaget' from Intel ME System Tools. The version is typically displayed as a numeric build such as 11.0.x, 11.10.x, 11.20.x, or 12.0.x.
    Affected if Unable to retrieve the firmware version indicates AMT may not be accessible or properly configured for version detection.
  4. Compare installed version against affected ranges
    If the firmware version is obtained, compare it to the following vulnerable ranges: 11.0 to 11.8.59 (inclusive), 11.10 to 11.11.59, 11.20 to 11.22.59, or 12.0.0 to 12.0.19. Any version within these ranges is affected.
    Affected if The installed firmware version falls within any of the four affected ranges listed in the CVE.

A system is affected only if it has Intel AMT hardware present, AMT is accessible on the network, and the installed firmware version matches one of the vulnerable version ranges.

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.60 / 11.11.60 / 11.22.60 or later
Fixed in 11.8.6011.11.6011.22.60
Interim mitigation

Update Intel AMT firmware to version 11.8.60, 11.11.60, 11.22.60, or 12.0.20 or later to remediate this vulnerability. If AMT is not required, consider disabling it to reduce the attack surface.

Fix this in Active Management Technology Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing3.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,050
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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