CVE-2020-8747
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 · uneditedOut-of-bounds read in subsystem for Intel(R) AMT 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 and/or 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 confidenceOut-of-bounds read vulnerability in Intel Active Management Technology (AMT) subsystem allows unauthenticated network attackers to read memory beyond intended boundaries, potentially disclosing sensitive system information or causing denial of service.
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< 11.8.80>= 11.12.0, < 11.12.80>= 11.22.0, < 11.22.80>= 12.0, < 12.0.70>= 14.0, < 14.0.45all versionsCVSS 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
- High
CVSS:3.1/AV:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check if Intel AMT is enabled on the systemOn Windows, run `wmic /namespace:\\root\wmi path Intel_AMT_FirmwareVersion get /value` or check the Intel Management Engine BIOS Extension (MEBx) configuration. On Linux, check for the presence of MEI devices: `ls /dev/mei*` or `ls /sys/class/mei/`Affected if Intel AMT is enabled and present on the system (vulnerability only applies if AMT is active)
-
Identify the Intel AMT firmware versionRun `wmic /namespace:\\root\IntelAMT path AMT_FirmwareVersion get /value` on Windows, or on Linux use the mei-fw-version tool or read from `/sys/class/mei/*/fw_version`. The version may also be visible in MEBx during boot.Affected if The firmware version falls into 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, or >= 14.0 and < 14.0.45
-
Check for NetApp Cloud Backup installationOn Windows, review installed programs via Control Panel or `Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*`. On Linux, check package manager listings or look for NetApp Cloud Backup processes or service files.Affected if NetApp Cloud Backup (formerly NetApp AltaVault) is installed on the system, as all versions are affected
-
Verify AMT network interface accessibilityCheck if ports 16992-16994 (Intel AMT HTTP/HTTPS interfaces) are listening or accessible on the system using `netstat -an | findstr "1699"` or a port scanner. Review firewall rules and network configuration.Affected if The Intel AMT network interface is exposed and accessible, which is required for the unauthenticated network attacker to exploit the flaw
The system is affected if Intel AMT is enabled with a firmware version in the vulnerable ranges, or if NetApp Cloud Backup is installed, and the AMT interface is network-accessible for remote exploitation.
Generated from the published advisory. Verify against your own configuration.
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 · scoped11.8.8011.12.8011.22.80
Update Intel AMT firmware to version 11.8.80, 11.12.80, 11.22.80, 12.0.70, 14.0.45 or later. If immediate patching is not feasible, restrict network access to AMT management interfaces using firewall rules or network segmentation.
Upgrade Intel AMT firmware to version 11.8.80, 11.12.80, 11.22.80, or 12.0.70 (or later) depending on your current version branch
- 1. Identify the Intel AMT version currently running on affected systems using the AMT firmware version check utility or BIOS/UEFI settings
- 2. Access the Intel Management Engine (ME) firmware update mechanism - typically through Intel Management Engine BIOS Extension (MEBX) or Intel Endpoint Management Assistant (EMA)
- 3. Obtain the Intel AMT firmware update package from Intel's official support site (www.intel.com) or your system OEM (Dell, HP, Lenovo, etc.)
- 4. Apply the firmware update to upgrade to version 11.8.80, 11.12.80, 11.22.80, or 12.0.70 or later depending on your current major version branch
- 5. After update, verify the new firmware version is installed correctly and AMT is functioning normally
- 6. For Cloud Backup (all versions), contact Intel support for specific patch availability as this product is end-of-life
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2020-8747 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-8747 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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