CVE-2020-8674
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 DHCPv6 subsystem in Intel(R) AMT and Intel(R)ISM versions before 11.8.77, 11.12.77, 11.22.77, 12.0.64 and 14.0.33 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 confidenceOut-of-bounds read vulnerability in the DHCPv6 subsystem of Intel Active Management Technology (AMT) and Intel Standard Manageability (ISM). An unauthenticated remote attacker on the network can potentially read sensitive information from memory beyond buffer boundaries through malformed DHCPv6 packets.
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.0, < 11.8.77>= 11.10, < 11.12.77>= 11.20, < 11.22.77>= 12.0, < 12.0.64>= 14.0, < 14.0.33>= 11.0, < 11.8.77>= 11.10, < 11.12.77>= 11.20, < 11.22.77>= 12.0, < 12.0.64>= 14.0, < 14.0.33CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Intel AMT or ISM is presentCheck if Intel AMT/ISM is enabled on the system - access the Intel Management Engine BIOS Extension (MEBX) during boot or check via the Intel AMT Web Interface if configuredAffected if Intel AMT or ISM is not present on the system, the vulnerability does not apply
-
Determine the Intel AMT/ISM firmware versionAccess the Intel AMT Web Interface or MEBX and locate the firmware version information. Compare the installed version against the affected ranges: 11.0 to 11.8.76, 11.10 to 11.12.76, 11.20 to 11.22.76, 12.0 to 12.0.63, or 14.0 to 14.0.32Affected if The installed version falls within any of the vulnerable version ranges listed
-
Confirm DHCPv6 is enabled in AMT configurationCheck the Intel AMT network configuration settings via the Web Interface or MEBX to determine if DHCPv6 is enabled. The vulnerability only affects systems with DHCPv6 functionality activeAffected if DHCPv6 is enabled and the firmware version is within the affected ranges
The system is affected only if Intel AMT or ISM is present, the firmware version is within one of the vulnerable version ranges, and DHCPv6 is enabled in the AMT configuration.
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.7711.12.7711.22.77
Update Intel AMT/ISM firmware to version 11.8.77, 11.12.77, 11.22.77, 12.0.64, 14.0.33 or later. In enterprise environments, apply via BIOS update, Intel ME firmware update, or AMT provisioning tools.
- 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-8674 — 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-8674 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