CVE-2020-0594
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 IPv6 subsystem in Intel(R) AMT and Intel(R) ISM versions before 11.8.77, 11.12.77, 11.22.77 and 12.0.64 may allow an unauthenticated user to potentially enable escalation of privilege 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 IPv6 subsystem of Intel Active Management Technology (AMT) and Intel Standard Manageability (ISM) firmware allows unauthenticated remote attackers to potentially escalate privileges via network access. Affected versions include those before 11.8.77, 11.12.77, 11.22.77, and 12.0.64.
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>= 11.0, < 11.8.77>= 11.10, < 11.12.77>= 11.20, < 11.22.77>= 12.0, < 12.0.64CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Verify Intel AMT or ISM is presentAccess the system BIOS or Intel Management Engine (ME) interface and look for Intel Active Management Technology or Intel Standard Manageability entries in the firmware or system information.Affected if Intel AMT or ISM is not found on the system, the vulnerability does not apply.
-
Check AMT/ISM firmware versionAccess the Intel AMT/ISM web interface (typically at https://localhost:16992 or https://localhost:16993 for local access) or use the Intel Management and Configuration interface. Navigate to the firmware version information.Affected if The firmware version cannot be determined, assume potentially affected.
-
Compare version against vulnerable rangesCompare the installed firmware version number to the affected ranges: versions before 11.8.77, 11.10.x before 11.12.77, 11.20.x before 11.22.77, and 12.0.x before 12.0.64.Affected if The installed version falls within any of these ranges: >= 11.0 and < 11.8.77; >= 11.10 and < 11.12.77; >= 11.20 and < 11.22.77; or >= 12.0 and < 12.0.64.
-
Confirm IPv6 is enabledIn the Intel AMT/ISM configuration settings, verify whether IPv6 support or the IPv6 network stack is enabled in the firmware network settings.Affected if IPv6 is disabled at the firmware level, the attack surface for this specific vulnerability may be reduced, though firmware updates are still recommended.
The system is affected if Intel AMT or ISM firmware is present and its version falls within the vulnerable version ranges before the fixed releases (11.8.77, 11.12.77, 11.22.77, or 12.0.64).
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.7711.12.7711.22.77
Update Intel AMT/ISM firmware to version 11.8.77, 11.12.77, 11.22.77, or 12.0.64 or later to remediate this critical vulnerability.
Intel AMT/ISM firmware version 11.8.77 or later (11.0 branch), 11.12.77 or later (11.10 branch), 11.22.77 or later (11.20 branch), or 12.0.64 or later (12.0 branch)
- Identify the current version of Intel AMT or ISM firmware running on affected systems
- Access the system firmware/BIOS configuration or Intel Management Engine (ME) interface to check the AMT version
- Determine which version branch the current firmware is on (11.0.x, 11.10.x, 11.20.x, or 12.0.x)
- Obtain the appropriate firmware update from the system manufacturer (OEM) - Intel provides generic updates but OEM-specific firmware is recommended
- Apply the firmware update following the manufacturer's recommended procedure, typically through: BIOS/UEFI update, Intel Management Engine Interface (MEI) tool, or OEM management console
- Verify the update was successful by checking the firmware version after reboot
- Confirm the updated version meets or exceeds the minimum fixed version for your branch: 11.8.77, 11.12.77, 11.22.77, or 12.0.64
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-0594 — 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-0594 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