CVE-2017-5705
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 · uneditedMultiple buffer overflows in kernel in Intel Manageability Engine Firmware 11.0/11.5/11.6/11.7/11.10/11.20 allow attacker with local access to the system to execute arbitrary code.
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 confidenceMultiple buffer overflow vulnerabilities exist in the kernel of Intel Manageability Engine (ME) Firmware versions 11.0 through 11.20. An attacker with local access to the system can exploit these buffer overflows to execute arbitrary code with kernel-level or Ring -2 (ME) privileges, achieving full system compromise.
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.5= 11.6= 11.7= 11.10= 11.20CVSS 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.0/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.
-
Confirm Intel ME is presentUse system information tools such as 'meinfo' (Linux/Windows), Intel ME Info tool, or check BIOS/UEFI information to verify Intel Manageability Engine firmware is installed on the system.Affected if Intel Manageability Engine is not present on the system, the CVE does not apply.
-
Retrieve Intel ME Firmware versionRun the Intel ME Info tool (meinfo.exe on Windows or meinfo on Linux), or use 'dmidecode -t 4' on Linux, or check the System Information utility in Windows to obtain the installed Intel ME Firmware version number.Affected if Unable to retrieve a version number indicates Intel ME may not be accessible or may be disabled.
-
Compare installed version to affected versionsMatch the retrieved firmware version against the affected versions: 11.0, 11.5, 11.6, 11.7, 11.10, and 11.20. Ensure an exact version match comparison.Affected if The installed version exactly matches any of these: 11.0, 11.5, 11.6, 11.7, 11.10, or 11.20.
-
Verify local or physical access is possibleAssess whether an attacker could gain local or physical access to the system, as the CVE requires local access to exploit the buffer overflow vulnerabilities.Affected if The system allows local or physical access to untrusted users, which combined with an affected ME version creates exposure to this vulnerability.
A system is affected if Intel Manageability Engine Firmware is installed with version exactly matching 11.0, 11.5, 11.6, 11.7, 11.10, or 11.20 and an attacker could potentially gain local access.
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 dataApply Intel's firmware updates for the Manageability Engine to patched versions. Restrict physical and local access to affected systems as a compensating control until patches can be deployed.
- 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-2017-5705 — 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-5705 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