dbcve.org
Active Management Technology FirmwareOperating system · Intel

CVE-2017-5697

MEDIUM · 6.5 CVSS v3.1 Published 2017-06-14
Fix available
A fix is available. Upgrade to 9.1.40.1000 / 9.5.60.1952 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
Insufficient clickjacking protection in the Web User Interface of Intel AMT firmware versions before 9.1.40.1000, 9.5.60.1952, 10.0.50.1004, 11.0.0.1205, and 11.6.25.1129 potentially allowing a remote attacker to hijack users web clicks via attacker's crafted web page.

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 confidence

This is a clickjacking vulnerability in the Intel AMT (Active Management Technology) web interface. The web application lacks proper X-Frame-Options or Content Security Policy frame-ancestors headers, allowing an attacker to embed the Intel AMT UI in an invisible iframe on a malicious page. When users click on the attacker's page, they are actually interacting with the AMT interface, potentially enabling unauthorized actions.

MitigationImplement X-Frame-Options: DENY or SAMEORIGIN header and/or Content-Security-Policy with frame-ancestors directive on the Intel AMT web server, or update firmware to one of the patched versions listed (9.1.40.1000, 9.5.60.1952, 10.0.50.1004, 11.0.0.1205, or 11.6.25.1129 or later).

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
Active Management Technology FirmwareOperating system
Affected:>= 9.1, < 9.1.40.1000>= 9.5, < 9.5.60.1952>= 10.0, < 10.0.50.1004>= 11.0, < 11.0.0.1205>= 11.6, < 11.6.25.1129

CVSS 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
Required
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Intel AMT is enabled on the system
    Check if Intel AMT (Active Management Technology) is provisioned and running. On Windows, open Command Prompt and run 'wmic /namespace:\\root\cimv2\intel_mc path Intel_AMT_Instance call GetSystemCreationClassName' or check BIOS for Intel AMT configuration options under 'Intel AMT' or 'Active Management Technology' settings.
    Affected if Intel AMT is not present or not provisioned, the system is not affected by this vulnerability.
  2. Identify Intel AMT firmware version
    Access the Intel AMT web interface via its IP address (typically on port 16992 or 16993) or use the Intel Management Engine BIOS Interface. Alternatively, run 'wmic /namespace:\\root\cimv2\intel_mc path Intel_AMT_ProductPackage GET Version' from Windows to retrieve the firmware version.
    Affected if The installed version falls within any of these ranges: >= 9.1 and < 9.1.40.1000; >= 9.5 and < 9.5.60.1952; >= 10.0 and < 10.0.50.1004; >= 11.0 and < 11.0.0.1205; or >= 11.6 and < 11.6.25.1129.
  3. Verify web interface is accessible
    Open a browser and navigate to the AMT web interface URL (for example, https://<amt_ip>:16993). Confirm the login page or status page loads successfully.
    Affected if The web interface is not accessible (disabled or blocked), the clickjacking flaw cannot be exploited.
  4. Check for missing X-Frame-Options header
    Using a browser's developer tools, curl, or a web proxy, perform a GET request to the Intel AMT web interface and inspect the HTTP response headers. Look for the 'X-Frame-Options' header.
    Affected if The response headers do NOT include 'X-Frame-Options: DENY' or 'X-Frame-Options: SAMEORIGIN', the interface is vulnerable to clickjacking.

A system is affected if Intel AMT is enabled with a vulnerable firmware version (within the affected ranges) AND the web interface is accessible without X-Frame-Options or CSP frame-ancestors headers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 9.1.40.1000 / 9.5.60.1952 / 10.0.50.1004 or later
Fixed in 9.1.40.10009.5.60.195210.0.50.1004
Interim mitigation

Implement X-Frame-Options: DENY or SAMEORIGIN header and/or Content-Security-Policy with frame-ancestors directive on the Intel AMT web server, or update firmware to one of the patched versions listed (9.1.40.1000, 9.5.60.1952, 10.0.50.1004, 11.0.0.1205, or 11.6.25.1129 or later).

Fix this in Active Management Technology Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-5697 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-5697 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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