dbcve.org
Secure Firewall Threat DefenseApplication · Cisco

CVE-2017-6625

HIGH · 7.1 CVSS v3.0 Published 2017-05-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
Remotely reachable 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
A "Cisco Firepower Threat Defense 6.0.0 through 6.2.2 and Cisco ASA with FirePOWER Module Denial of Service" vulnerability in the access control policy of Cisco Firepower System Software could allow an authenticated, remote attacker to cause an affected system to stop inspecting and processing packets, resulting in a denial of service (DoS) condition. The vulnerability is due to improper SSL policy handling by the affected software when packets are passed through the sensing interfaces of an affected system. An attacker could exploit this vulnerability by sending crafted packets through a targeted system. This vulnerability affects Cisco Firepower System Software that is configured with the SSL policy feature. Cisco Bug IDs: CSCvc84361.

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 denial of service vulnerability in Cisco Firepower System Software (versions 6.0.0-6.2.2) and Cisco ASA with FirePOWER Module. The flaw exists in the access control policy's SSL policy handling when packets traverse sensing interfaces. An authenticated remote attacker can send specially crafted packets to cause the affected system to stop inspecting and processing traffic, resulting in a DoS condition.

MitigationUpgrade Cisco Firepower System Software to a version beyond 6.2.2 that contains the fix for CSCvc84361. If immediate patching is not possible, consider disabling the SSL policy feature in the access control policy as a temporary workaround, though this may impact security inspection capabilities.

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
Secure Firewall Threat DefenseApplication
Affected:= 6.0.0= 6.0.1= 6.1.0= 6.1.0.2= 6.2.0= 6.2.1= 6.2.2

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

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/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. Identify the installed Cisco Firepower Threat Defense version
    Run 'show version' or check the system management interface to retrieve the currently installed Firepower Threat Defense version number
    Affected if The installed version matches 6.0.0, 6.0.1, 6.1.0, 6.1.0.2, 6.2.0, 6.2.1, or 6.2.2
  2. Confirm SSL policy is configured in the access control policy
    Access the Firepower Management Center and navigate to Policies > Access Control, then inspect whether an SSL policy is assigned to any access control rule
    Affected if An SSL policy is attached to an active access control policy and traffic is being matched against it
  3. Verify sensing interfaces are in use
    Check the interface configuration to confirm that sensing interfaces (passive or inline tap mode) are actively deployed for traffic inspection
    Affected if Sensing interfaces are configured and actively receiving traffic that traverses the SSL policy inspection point
  4. Review system health and traffic inspection status
    Monitor the system dashboard and health monitor for sudden drops in traffic inspection throughput or SSL inspection failures
    Affected if Traffic inspection has stopped or dropped to zero while traffic is still reaching the interface

You are affected if your Firepower Threat Defense version is between 6.0.0 and 6.2.2 inclusive, and you have an SSL policy configured in your access control policy that is actively inspecting traffic on sensing interfaces.

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

Upgrade Cisco Firepower System Software to a version beyond 6.2.2 that contains the fix for CSCvc84361. If immediate patching is not possible, consider disabling the SSL policy feature in the access control policy as a temporary workaround, though this may impact security inspection capabilities.

Fix this in Secure Firewall Threat Defense Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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