CVE-2017-5712
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 · uneditedBuffer overflow in Active Management Technology (AMT) in Intel Manageability Engine Firmware 8.x/9.x/10.x/11.0/11.5/11.6/11.7/11.10/11.20 allows attacker with remote Admin access to the system to execute arbitrary code with AMT execution privilege.
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 confidenceBuffer overflow vulnerability in Intel Active Management Technology (AMT) firmware versions 8.x through 11.20 allows an attacker with remote administrative access to execute arbitrary code with AMT execution privileges. The vulnerability resides in the Manageability Engine firmware, which operates below the operating system at a privileged hardware level.
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>= 8.0.0.0, <= 8.1.71.3608>= 9.0.0.0, <= 9.1.41.3024>= 10.0.0.0, <= 10.0.55.3000= 11.0= 11.5= 11.6= 11.7= 11.10= 11.20all versionsall versionsall versionsall versionsall versionsall versionsall 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
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 Manageability Engine is presentCheck system information or BIOS/UEFI settings for Intel Active Management Technology (AMT) or Intel Management Engine (ME) entries. On Windows, this may appear in device manager or system information. On Linux, tools like 'meinfo' or 'intel-mei-dkms' package information may show presence.Affected if Intel AMT or Manageability Engine firmware is not present on the system, then this CVE does not apply.
-
Confirm AMT is enabledAccess BIOS/UEFI settings during boot and look for Intel AMT or Manageability Engine configuration options. In Windows, check Intel Management Engine interface or enterprise management tools if available.Affected if AMT is disabled in BIOS/UEFI and the Manageability Engine is not running, the vulnerability cannot be exploited.
-
Identify the Intel Manageability Engine firmware versionUse Intel management tools (Intel ME System Tools, Intel Management Engine Interface driver), or check BIOS/UEFI firmware information page for the ME/AMT firmware version string.Affected if The installed version falls within any of these ranges: 8.0.0.0 to 8.1.71.3608, 9.0.0.0 to 9.1.41.3024, 10.0.0.0 to 10.0.55.3000, or equals 11.0, 11.5, 11.6, 11.7, 11.10, or 11.20.
-
Check if system uses affected Asus Z170 motherboard firmwareIdentify the motherboard model through system information, BIOS startup screen, or physical board labeling. Affected models are: Z170 Premium, Z170 Deluxe, Z170 Pro, Z170 A, Z170 Ar, Z170 E.Affected if The system is one of the listed Asus Z170 motherboards, then all firmware versions are affected regardless of Intel ME version.
-
Verify remote administrative access vectorConfirm whether network access to AMT web interface or SOL (Serial Over LAN) is exposed. Check if ports 16992-16994 (default AMT ports) are accessible on the network.Affected if Remote network access to AMT is available and the system meets version or model criteria above, then it is vulnerable.
A system is affected if it has Intel AMT enabled with vulnerable Manageability Engine firmware (versions listed above) or is an Asus Z170 motherboard model with AMT present, and network access to AMT is available to an attacker.
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 dataUpdate Intel Manageability Engine Firmware to a patched version provided by Intel through their support channels or enterprise management tools. If AMT is not required, disable it in BIOS/UEFI firmware settings as a defense-in-depth measure.
- Consultation4.0 h
- Implementation2.0 h
- Testing2.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 $2,912.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-5712 — 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-2017-5712 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