CVE-2020-8760
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 · uneditedInteger overflow in subsystem for Intel(R) AMT versions before 11.8.80, 11.12.80, 11.22.80, 12.0.70, 14.0.45 may allow a privileged user to potentially enable escalation of privilege via local 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 confidenceInteger overflow vulnerability in Intel Active Management Technology (AMT) subsystem affecting versions before 11.8.80, 11.12.80, 11.22.80, 12.0.70, and 14.0.45. A privileged user with local access can exploit the overflow to escalate privileges on affected systems.
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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Intel AMT is presentLocate Intel Active Management Technology on the system. This is a firmware/BIOS feature, not a standard software install. Check system BIOS/UEFI settings, or use system information tools that expose AMT status.Affected if AMT is not present on the system, the vulnerability does not apply.
-
Verify AMT is enabledConfirm that Intel AMT is actively running, not just present in BIOS. AMT must be in an enabled operational state for the overflow to be exploitable.Affected if AMT is disabled or not provisioned, the vulnerability is not accessible to local attackers.
-
Determine AMT firmware versionRetrieve the installed Intel AMT firmware version. This is typically found in AMT BIOS settings, Intel ME/AMT system information, or via management interfaces that query the AMT subsystem.Affected if Unable to determine version - treat as potentially affected if AMT is enabled.
-
Compare version to affected rangesMatch the installed AMT firmware version against: < 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.45Affected if The installed version falls into any of these ranges - the system is affected by CVE-2020-8760.
-
Check for NetApp Cloud Backup installationDetermine if Netapp Cloud Backup software is installed on the system.Affected if NetApp Cloud Backup is present (all versions are affected per the CVE).
The system is affected if Intel AMT is enabled AND the firmware version is below the fixed releases (11.8.80, 11.12.80, 11.22.80, 12.0.70, or 14.0.45), or if NetApp Cloud Backup is installed regardless of version.
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.
From vendor data11.8.8011.12.8011.22.80
Apply Intel-provided firmware updates to upgrade AMT to version 11.8.80, 11.12.80, 11.22.80, 12.0.70, or 14.0.45 or later. Restrict physical/local access to systems with AMT enabled until patching is complete.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-8760 — 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-8760 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