dbcve.org
Active Management Technology FirmwareOperating system · Intel

CVE-2020-8754

HIGH · 7.5 CVSS v3.1 Published 2020-11-12
Fix available
A fix is available. Upgrade to 11.8.80 / 11.12.80 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
Out-of-bounds read in subsystem for Intel(R) AMT, Intel(R) ISM versions before 11.8.80, 11.12.80, 11.22.80, 12.0.70 and 14.0.45 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

An out-of-bounds read vulnerability exists in Intel Active Management Technology (AMT) and Intel Standard Manageability (ISM) firmware. An unauthenticated remote attacker with network access can exploit this flaw to read memory contents beyond buffer boundaries, potentially disclosing sensitive information.

MitigationUpdate Intel AMT/ISM firmware to version 11.8.80, 11.12.80, 11.22.80, 12.0.70, 14.0.45 or later. If patching is not immediately possible, restrict network access to management interfaces and disable AMT where not required.

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.8.80>= 11.12.0, < 11.12.80>= 11.22.0, < 11.22.80>= 12.0, < 12.0.70>= 14.0, < 14.0.45
Cloud BackupApplication
Affected:all versions
Standard ManageabilityApplication
Affected:< 11.8.80>= 11.12.0, < 11.12.80>= 11.22.0, < 11.22.80>= 12.0, < 12.0.70>= 14.0, < 14.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
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. Check if Intel AMT is enabled
    On the target system, access the BIOS/UEFI settings or use the Intel Management Engine BIOS Extension (MEBX) interface during boot, or query the system via Intel's AMT status tool (amttool, or via WS-Management: Get-CimInstance -ClassName Win32_ComputerSystem). Look for AMT status or provisioning state.
    Affected if AMT is present and provisioned (even if in user-controlled mode)
  2. Determine Intel AMT/ISM firmware version
    If AMT is present, access the AMT web interface (typically on port 16992/16993) or use the Intel Management Engine Interface (MEI) via: 'mecli -version' or 'fwts me -v' on Linux; on Windows check via Device Manager or Intel SA Update Tool. Record the firmware build version.
    Affected if The firmware version falls within any of these vulnerable ranges: < 11.8.80; >= 11.12.0 and < 11.12.80; >= 11.22.0 and < 11.22.80; >= 12.0 and < 12.0.70; >= 14.0 and < 14.0.45
  3. Check for NetApp Cloud Backup installation
    Search for NetApp Cloud Backup (formerly AltaVault) by checking installed programs on the system: on Windows, review Programs and Features or run 'Get-WmiObject -Class Win32_Product'; on Linux, check rpm/dpkg packages for 'netapp' or 'altavault' or review /opt directory for NetApp software.
    Affected if NetApp Cloud Backup is installed (all versions are affected)
  4. Verify network exposure of AMT interfaces
    Scan internal network or review firewall rules for open ports 16992 (HTTP) and 16993 (HTTPS) which serve AMT/ISM web interfaces. Check if these ports are accessible from non-management network segments.
    Affected if Port 16992/16993 is exposed to network segments where untrusted users exist

A system is affected if it runs any version of Intel AMT/ISM firmware matching the vulnerable version ranges, or has NetApp Cloud Backup installed, and the management interface is network-accessible.

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.80 / 11.12.80 / 11.22.80 or later
Fixed in 11.8.8011.12.8011.22.80
Interim mitigation

Update Intel AMT/ISM firmware to version 11.8.80, 11.12.80, 11.22.80, 12.0.70, 14.0.45 or later. If patching is not immediately possible, restrict network access to management interfaces and disable AMT where not required.

Fix this in Active Management Technology Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
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,480.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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