dbcve.org
Active Management Technology FirmwareOperating system · Intel

CVE-2019-0131

HIGH · 8.1 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 →
86/100
Remediation priority · High
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 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 denial of service or information disclosure via adjacent 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

Intel AMT (Active Management Technology) contains an insufficient input validation vulnerability in a subsystem that allows unauthenticated users with adjacent network access to potentially cause denial of service or obtain information disclosure. The vulnerability affects AMT versions prior to 11.8.70, 11.11.70, 11.22.70, and 12.0.45.

MitigationUpdate Intel AMT firmware to version 11.8.70, 11.11.70, 11.22.70, 12.0.45 or later to remediate the vulnerability. If updates cannot be applied immediately, restrict network access to AMT interfaces to reduce the adjacent 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.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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
High

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/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 firmware version
    Access the Intel AMT web interface via https://<hostname>:16992 or use the command line tool 'meutil version' (Linux) or check via Intel ME Information in Device Manager (Windows). The firmware version is typically displayed as a build number in the format XX.Y.Y.ZZ.
    Affected if The displayed version falls within any of these 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. Compare your version number against these thresholds.
  2. Confirm Intel AMT is provisioned and enabled
    In Windows, open Device Manager and expand 'System devices' to check for 'Intel Management Engine Interface' or 'Intel Active Management Technology'. In Linux, run 'ls /dev/mei*' or 'dmesg | grep mei' to confirm the Management Engine Interface driver is loaded.
    Affected if Intel AMT appears in Device Manager or the /dev/mei device exists, indicating AMT hardware is present and the driver is loaded.
  3. Check if AMT network interface is accessible
    From a system on the same network segment, attempt to access the AMT web interface by browsing to https://<target-ip>:16992 or running 'nc -zv <target-ip> 16992' to test port 16992 connectivity. This validates the adjacent network condition required for exploitation.
    Affected if Port 16992 (or 16993 for secure) responds, meaning the AMT web interface is reachable from your testing position on the network.
  4. Verify AMT operational status
    In the AMT web interface, navigate to the 'General Information' or 'Intel AMT' status page. Alternatively, use the command 'meutil status' (if available) to check if AMT state shows as 'Enabled' or 'Operational'.
    Affected if AMT status shows as Enabled, Operational, or running, confirming the vulnerable subsystem is active.

A system is affected if it has Intel AMT hardware present, AMT is enabled and operational, the AMT web interface is network-accessible, and the firmware version matches one of the vulnerable version 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

Update Intel AMT firmware to version 11.8.70, 11.11.70, 11.22.70, 12.0.45 or later to remediate the vulnerability. If updates cannot be applied immediately, restrict network access to AMT interfaces to reduce the adjacent attack surface.

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-0131 — 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-0131 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