dbcve.org
Active Management Technology FirmwareOperating system · Intel

CVE-2020-0595

CRITICAL · 9.8 CVSS v3.1 Published 2020-06-15
Fix available
A fix is available. Upgrade to 11.8.77 / 11.12.77 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
Use after free in IPv6 subsystem in Intel(R) AMT and Intel(R) ISM versions before 11.8.77, 11.12.77, 11.22.77 and 12.0.64 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 · moderate confidence

A use-after-free vulnerability exists in the IPv6 subsystem of Intel Active Management Technology (AMT) and Intel Standard Manageability (ISM). This memory corruption flaw allows an unauthenticated remote attacker to potentially execute arbitrary code or escalate privileges via network access.

MitigationUpdate Intel AMT/ISM to version 11.8.77, 11.12.77, 11.22.77, 12.0.64 or later. Additionally, network segmentation and restricting AMT access to trusted networks can reduce 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.77>= 11.10, < 11.12.77>= 11.20, < 11.22.77>= 12.0, < 12.0.64
Service ManagerApplication
Affected:>= 11.0, < 11.8.77>= 11.10, < 11.12.77>= 11.20, < 11.22.77>= 12.0, < 12.0.64

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. Identify Intel AMT/ISM presence
    Check system information or BIOS for Intel AMT or Intel Standard Manageability. On Windows, run 'wmic baseboard get product,manufacturer' or check BIOS/UEFI settings for Intel AMT configuration options. On Linux, check 'ls /dev/mei*' or 'dmesg | grep -i mei' for Intel Management Engine interface.
    Affected if Intel AMT or ISM is not present on the system, the vulnerability does not apply.
  2. Determine AMT/ISM firmware version
    Access the Intel AMT web interface (typically at https://localhost:16992 or https://<hostname>:16992) and navigate to the firmware version information page. Alternatively, use the Intel Manageability Commander tool or run 'wmic /namespace:\\root\cimv2\Intel_AMT get Version' if available.
    Affected if The installed version falls within any of these ranges: >= 11.0 and < 11.8.77, OR >= 11.10 and < 11.12.77, OR >= 11.20 and < 11.22.77, OR >= 12.0 and < 12.0.64.
  3. Verify IPv6 is enabled for AMT
    Access the Intel AMT configuration via the web interface or Intel Management Engine Interface (MEI) and check the IPv6 network settings. Ensure IPv6 is listed as enabled in the AMT network configuration.
    Affected if IPv6 is enabled in the AMT network settings. The vulnerability exists in the IPv6 subsystem, so if IPv6 is disabled at the AMT level, the attack surface is reduced.
  4. Check network exposure of AMT services
    Scan the management interface IP addresses accessible from the network using 'nmap -p 16992,16993 <target>' or check firewall rules and network ACLs that allow access to ports 16992 (HTTP) and 16993 (HTTPS).
    Affected if The AMT web interface (ports 16992/16993) is accessible from untrusted network segments. The vulnerability is remotely exploitable via network access.

If Intel AMT or ISM firmware version is 11.x before 11.8.77/11.12.77/11.22.77 (depending on the branch) or 12.x before 12.0.64, and IPv6 is enabled with network accessibility, the system is affected by this CVE.

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.77 / 11.12.77 / 11.22.77 or later
Fixed in 11.8.7711.12.7711.22.77
Interim mitigation

Update Intel AMT/ISM to version 11.8.77, 11.12.77, 11.22.77, 12.0.64 or later. Additionally, network segmentation and restricting AMT access to trusted networks can reduce attack surface.

Recommended fix High confidence

Upgrade to Intel AMT/ISM version 11.8.77 (for 11.0.x branch), 11.12.77 (for 11.10.x branch), 11.22.77 (for 11.20.x branch), or 12.0.64 (for 12.0.x branch) - whichever corresponds to your current version branch

  1. 1. Identify the current Intel AMT/ISM version by accessing the Intel Management Engine (ME) firmware version through the BIOS, Intel Management Engine Interface (MEI), or AMT configuration utility.
  2. 2. Determine which version branch your current firmware falls into: 11.0.x, 11.10.x, 11.20.x, or 12.0.x.
  3. 3. For systems on version 11.0.x (>=11.0, <11.8.77), upgrade to version 11.8.77 or later.
  4. 4. For systems on version 11.10.x (>=11.10, <11.12.77), upgrade to version 11.12.77 or later.
  5. 5. For systems on version 11.20.x (>=11.20, <11.22.77), upgrade to version 11.22.77 or later.
  6. 6. For systems on version 12.0.x (>=12.0, <12.0.64), upgrade to version 12.0.64 or later.
  7. 7. Obtain the firmware update from your system manufacturer (OEM) - Intel provides firmware through OEM vendors (Lenovo, Dell, HP, etc.) as referenced in the support sites.
  8. 8. Apply the firmware update following your OEM's specific instructions, typically via BIOS update, Intel ME firmware update tool, or AMT provisioning process.
Caveat Firmware updates to Intel AMT may require re-provisioning if changing major versions; ensure AMT configuration is backed up before upgrade

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

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-2020-0595 — 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-2020-0595 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