dbcve.org
Firepower Threat DefenseApplication · Cisco

CVE-2017-6632

HIGH · 7.5 CVSS v3.0 Published 2017-05-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 vulnerability in the logging configuration of Secure Sockets Layer (SSL) policies for Cisco FirePOWER System Software 5.3.0 through 6.2.2 could allow an unauthenticated, remote attacker to cause a denial of service (DoS) condition due to high consumption of system resources. The vulnerability is due to the logging of certain TCP packets by the affected software. An attacker could exploit this vulnerability by sending a flood of crafted TCP packets to an affected device. A successful exploit could allow the attacker to cause a DoS condition. The success of an exploit is dependent on how an administrator has configured logging for SSL policies for a device. This vulnerability affects Cisco FirePOWER System Software that is configured to log connections by using SSL policy default actions. Cisco Bug IDs: CSCvd07072.

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

A vulnerability in the SSL policy logging feature of Cisco FirePOWER System Software versions 5.3.0 through 6.2.2 allows an unauthenticated remote attacker to cause denial of service by sending a flood of crafted TCP packets. The vulnerability stems from excessive logging of certain TCP packets, consuming high system resources.

MitigationAdministrators should review and reconfigure SSL policy logging settings to disable logging for default actions, or upgrade to a patched software version.

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
Firepower Threat DefenseApplication
Affected:= 6.2_base
Secure Firewall Threat DefenseApplication
Affected:= 5.3.0= 5.4.0= 6.0.0= 6.0.1= 6.0.1.3= 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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 software version
    Use the system CLI or web interface to view the running version of Cisco FirePOWER System Software or Firepower Threat Defense. Common command: 'show version' or check the system dashboard.
    Affected if The installed version falls within 5.3.0 through 6.2.2 (including 5.3.0, 5.4.0, 6.0.0, 6.0.1, 6.0.1.3, 6.1.0, 6.1.0.2, 6.2.0, 6.2.1, 6.2.2, or 6.2_base)
  2. Locate SSL policy configuration
    Access the FirePOWER management console or FMC (Firepower Management Center) and navigate to the SSL policy settings. This is typically found under Policies > Access Control > SSL policy.
    Affected if An SSL policy exists and is actively applied to traffic inspection.
  3. Verify SSL policy logging settings
    Examine the SSL policy configuration to determine whether logging is enabled for default actions or specific rules. Look for logging options such as 'Log Default Action' or similar logging toggles within the SSL policy editor.
    Affected if Logging is enabled for default actions or for rules that process certain TCP packets.
  4. Confirm SSL policy is actively enforced
    Check if the SSL policy is assigned to an access control policy and actively applied to network traffic. Verify the policy is not in a disabled or standby state.
    Affected if The SSL policy with logging enabled is actively applied to traffic and not in a passive monitoring mode.

You are affected if your Cisco FirePOWER version is 5.3.0 through 6.2.2 AND you have an SSL policy with logging enabled for default actions or specific rules actively applied to traffic.

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

Administrators should review and reconfigure SSL policy logging settings to disable logging for default actions, or upgrade to a patched software version.

Fix this in Firepower Threat Defense Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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