dbcve.org
Advanced Malware ProtectionApplication · Cisco

CVE-2017-12317

MEDIUM · 6.7 CVSS v3.0 Published 2017-10-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Zero-click

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
The Cisco AMP For Endpoints application allows an authenticated, local attacker to access a static key value stored in the local application software. The vulnerability is due to the use of a static key value stored in the application used to encrypt the connector protection password. An attacker could exploit this vulnerability by gaining local, administrative access to a Windows host and stopping the Cisco AMP for Endpoints service. Cisco Bug IDs: CSCvg42904.

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

The Cisco AMP For Endpoints application for Windows stores a static encryption key in the application binary itself. This key encrypts the connector protection password. An attacker with local administrative access can stop the service and extract this static key from the application, potentially decrypting sensitive credentials.

MitigationApply the Cisco vendor patch when available. Until then, restrict administrative access to endpoints running Cisco AMP and monitor for unauthorized service stops.

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
Advanced Malware ProtectionApplication
Affected:= 3.1\(10\)= 3.1\(15\)= 4.0\(0\)= 4.0\(1\)= 4.0\(2\)= 4.1\(0\)= 4.1\(1\)= 4.1\(4\)= 4.2\(0\)= 4.2\(1\)= 4.3\(0\)= 4.3\(1\)

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
Local
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/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 checks

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

  1. Confirm Cisco AMP for Endpoints is installed
    Check for the presence of the Cisco AMP service on the Windows system. Open Services console (services.msc) and look for 'Cisco AMP for Endpoints' service, or check the installation directory (typically C:\Program Files\Cisco\AMP or C:\Program Files (x86)\Cisco\AMP).
    Affected if The Cisco AMP for Endpoints application is installed on the system.
  2. Identify the installed version
    Right-click the Cisco AMP executable (such as sfc.exe or ampdaemon.exe) in the installation directory, select Properties, and view the File Version. Alternatively, run 'wmic product get name,version' or check the Windows Registry under HKLM\SOFTWARE\Cisco\AMP for the version entry.
    Affected if The installed version matches one of the affected versions: 3.1(10), 3.1(15), 4.0(0), 4.0(1), 4.0(2), 4.1(0), 4.1(1), 4.1(4), 4.2(0), 4.2(1), 4.3(0), or 4.3(1).
  3. Verify the AMP service is running
    Open Services console and check the status of the 'Cisco AMP for Endpoints' service, or run 'sc query AmpService' from an elevated command prompt.
    Affected if The service is currently stopped, which could indicate attempted exploitation or that the binary has been tampered with.
  4. Inspect application binaries for static encryption key
    Examine the main Cisco AMP executable files in the installation directory using a hex editor or strings utility. Look for hardcoded cryptographic key patterns (typically 32-byte or 64-byte hex strings) that could serve as a static encryption key.
    Affected if Static encryption key patterns are found embedded in the application binaries.
  5. Review security logs for service manipulation
    Check Windows Event Viewer under Security and Application logs for event IDs related to service control (such as Event ID 7045 for new service installs) or look for logs indicating the Cisco AMP service was stopped unexpectedly.
    Affected if There are logs showing the AMP service was stopped or the binary was accessed by unauthorized administrative accounts.

You are affected if Cisco AMP for Endpoints is installed with a version matching any of the listed affected versions and the application binaries contain a hardcoded static encryption key.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Cisco vendor patch when available. Until then, restrict administrative access to endpoints running Cisco AMP and monitor for unauthorized service stops.

Fix this in Advanced Malware Protection Scoped from the published advisory
  • Consultation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,560
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-12317 — 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-12317 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