CVE-2020-0535
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 · uneditedImproper input validation in Intel(R) AMT versions before 11.8.76, 11.12.77, 11.22.77 and 12.0.64 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 confidenceImproper input validation vulnerability in Intel(R) AMT (Active Management Technology) allows unauthenticated remote attackers to potentially disclose sensitive information via network access due to insufficient validation of input parameters in the AMT subsystem.
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.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
- 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 is present and enabledCheck the system BIOS/UEFI settings under 'Intel Active Management Technology', 'Intel AMT', or 'Management Engine' configuration, or use the Intel Management Engine Interface (MEI) driver via Device Manager on Windows to confirm the hardware is presentAffected if Intel AMT is not present on the system (older consumer CPUs or disabled in BIOS), the system is not affected by this vulnerability since the flaw exists within the AMT subsystem itself
-
Retrieve the Intel AMT firmware versionAccess the AMT web interface (typically at https://localhost:16992 or https://16992), or use the Intel ME Info tool (meinfowin64.exe or Linux equivalent) from the Intel Driver and Support Assistant to query the firmware version. On Windows, also check via 'wmic /namespace:\\root\cimv2\intel_me path Intel_AMTManagementCapabilities' or the Intel AMT SDK tools if availableAffected if The version cannot be retrieved (AMT likely not enabled or not accessible), but if version is retrieved, proceed to version comparison
-
Compare installed version against affected rangesCompare the retrieved firmware version number to these vulnerable ranges: 11.0 through 11.8.76, 11.10 through 11.12.76, 11.20 through 11.22.76, or 12.0 through 12.0.63. If the version falls within any of these ranges, the system is vulnerableAffected if The installed AMT firmware version is greater than or equal to 11.0 but less than 11.8.77, OR greater than or equal to 11.10 but less than 11.12.77, OR greater than or equal to 11.20 but less than 11.22.77, OR greater than or equal to 12.0 but less than 12.0.64
A system is affected only if Intel AMT hardware is present, AMT firmware is enabled and accessible, and the installed firmware version falls within any of the four vulnerable version ranges specified in the CVE.
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
Upgrade Intel AMT firmware to version 11.8.76, 11.12.77, 11.22.77, or 12.0.64 or later to remediate the input validation vulnerability.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-0535 — 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-0535 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