dbcve.org
Active Management Technology FirmwareOperating system · Intel

CVE-2020-0596

HIGH · 7.5 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 →
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
Improper input validation in DHCPv6 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 information disclosure 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

Improper input validation exists in the DHCPv6 subsystem of Intel AMT (Active Management Technology) and ISM (Intel Standard Manageability). An unauthenticated remote attacker sending specially crafted DHCPv6 network packets could trigger the vulnerability, potentially leading to disclosure of sensitive information.

MitigationApply Intel's firmware updates: upgrade to version 11.8.77, 11.12.77, 11.22.77, or 12.0.64 or later. Network segmentation and firewall rules restricting DHCPv6 traffic to untrusted networks can provide interim defense-in-depth.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 or ISM is present
    Check system information or Intel utilities (Intel ME Info, Intel AMT Status, or system BIOS/UEFI settings) for the presence of Intel Active Management Technology or Intel Standard Manageability.
    Affected if Intel AMT or ISM is not installed on the system, the system is not affected.
  2. Identify the Intel AMT/ISM firmware version
    Access Intel MEBx (Management Engine BIOS Extension) via BIOS/UEFI during boot, or use Intel Management Engine firmware version tools. Compare the installed firmware version against the affected ranges: 11.0 to 11.8.76, 11.10 to 11.12.76, 11.20 to 11.22.76, or 12.0 to 12.0.63.
    Affected if The firmware version falls within any of the affected ranges listed.
  3. Verify DHCPv6 is enabled in AMT configuration
    Access Intel MEBx or AMT configuration settings and check the network configuration for DHCPv6 (IPv6 DHCP) status. DHCPv6 may be listed under Network Settings, IP Configuration, or Remote Configuration.
    Affected if DHCPv6 is enabled and the firmware version is in the affected range, the system is vulnerable to specially crafted DHCPv6 packets.
  4. Check network exposure of AMT management interface
    Review firewall rules and network segmentation to determine if the AMT management port (typically port 16992/16993 for HTTP/HTTPS) is exposed to untrusted networks, particularly via IPv6.
    Affected if AMT is reachable from untrusted networks and the version is vulnerable, an unauthenticated remote attacker could exploit this over the network.

The system is affected if it runs Intel AMT or ISM firmware versions 11.0-11.8.76, 11.10-11.12.76, 11.20-11.22.76, or 12.0-12.0.63 with DHCPv6 enabled and accessible over the network.

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

Apply Intel's firmware updates: upgrade to version 11.8.77, 11.12.77, 11.22.77, or 12.0.64 or later. Network segmentation and firewall rules restricting DHCPv6 traffic to untrusted networks can provide interim defense-in-depth.

Fix this in Active Management Technology Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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