dbcve.org
Active Management Technology FirmwareOperating system · Intel

CVE-2020-8746

MEDIUM · 6.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 →
70/100
Remediation priority · Elevated
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
Integer overflow 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 denial of service 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

An integer overflow vulnerability exists in the Intel Active Management Technology (AMT) subsystem in versions prior to 11.8.80, 11.12.80, 11.22.80, 12.0.70, and 14.0.45. An unauthenticated attacker with adjacent network access can exploit this overflow to cause a denial of service condition.

MitigationUpdate 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 possible, restrict network adjacency to trusted endpoints only.

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

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

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/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. Check if Intel AMT is enabled on the system
    Access the system BIOS/UEFI setup (usually press Del, F2, or F12 at boot) and look for Intel Active Management Technology or Intel AMT under Advanced or Security settings. On Windows, open Services (services.msc) and check for 'Intel(R) Active Management Technology' service (service name: 'Intel(R) AMT').
    Affected if Intel AMT is present and enabled in BIOS/UEFI or the Intel AMT service is running on Windows.
  2. Determine Intel AMT firmware version via Intel ME Info tool
    Download and run the Intel Management Engine Information Tool (Intel ME Info) or use the command 'wmic /namespace:\\root\cimv2\security\microsofttpm path Win32_TPM get *' or check via Intel AMT SDK. Alternatively, on some systems, the version is displayed in the BIOS under 'Intel AMT Version' or 'ME Version'.
    Affected if The firmware version displayed is one of the affected versions: < 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.
  3. Check for NetApp Cloud Backup installation on Windows
    Open Control Panel > Programs and Features, or use PowerShell command 'Get-WmiObject -Class Win32_Product | Where-Object {$_.Name -like "*Cloud Backup*"}' to list installed software. Look for 'NetApp Cloud Backup' or 'NetApp Cloud Backup (formerly AltaVault)' in the installed programs list.
    Affected if NetApp Cloud Backup is installed on the system (all versions are affected per the CVE).
  4. Verify network exposure of Intel AMT
    Check if ports 16992, 16993, 16994, 16995 (default Intel AMT ports) are open and accessible. Run 'netstat -an | findstr "1699"' or use a port scanner against localhost or the system's IP address. Also check firewall rules: 'netsh advfirewall firewall show rule name=all' for any AMT-related rules.
    Affected if Intel AMT ports are listening and accessible from the network (the vulnerability requires adjacent network access to exploit).

A system is affected if it has Intel AMT enabled with a firmware version falling within any of the vulnerable version ranges, or has NetApp Cloud Backup installed, and the relevant network ports are accessible to adjacent attackers.

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 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 possible, restrict network adjacency to trusted endpoints only.

Fix this in Active Management Technology Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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