dbcve.org
Secure Firewall Management CenterApplication · Cisco

CVE-2017-3885

MEDIUM · 5.9 CVSS v3.0 Published 2017-04-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
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 detection engine reassembly of Secure Sockets Layer (SSL) packets for Cisco Firepower System Software could allow an unauthenticated, remote attacker to cause a denial of service (DoS) condition because the Snort process consumes a high level of CPU resources. Affected Products: This vulnerability affects Cisco Firepower System Software running software releases 6.0.0, 6.1.0, 6.2.0, or 6.2.1 when the device is configured with an SSL policy that has at least one rule specifying traffic decryption. More Information: CSCvc58563. Known Affected Releases: 6.0.0 6.1.0 6.2.0 6.2.1.

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 packet detection engine reassembly for Cisco Firepower System Software allows an unauthenticated remote attacker to cause high CPU resource consumption by the Snort process, resulting in denial of service. The vulnerability is triggered when the device has an SSL policy configured with at least one traffic decryption rule.

MitigationApply the vendor-provided patch from Cisco for this vulnerability (CSCvc58563). If a patch is unavailable, consider disabling SSL decryption policies as a temporary workaround or upgrade to an unaffected software release.

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 Management CenterApplication
Affected:= 6.0.0= 6.1.0= 6.2.0= 6.2.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
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:H/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 product version
    Access the Firepower Management Center web interface and navigate to System > Updates, or use the CLI and run 'show version' to retrieve the software version.
    Affected if The version matches 6.0.0, 6.1.0, 6.2.0, or 6.2.1 exactly.
  2. Confirm the product is Cisco Secure Firewall Management Center
    Verify the device is running Cisco Firepower System Software (now known as Cisco Secure Firewall Management Center). Check the product name in the web interface header or CLI output.
    Affected if The product is Cisco Secure Firewall Management Center (formerly Firepower Management Center).
  3. Locate SSL decryption policies
    In the Firepower Management Center web interface, navigate to Policies > SSL Policy to view all configured SSL policies.
    Affected if At least one SSL policy exists in the system.
  4. Check for traffic decryption rules within SSL policies
    Open each SSL policy listed and examine the rule table. Look for rules with Action set to 'Decrypt' or 'Decrypt with Known Key' that apply to traffic inspection.
    Affected if Any SSL policy contains one or more rules configured to decrypt traffic.

A system is affected if it runs Cisco Secure Firewall Management Center version 6.0.0, 6.1.0, 6.2.0, or 6.2.1 AND has an SSL policy with at least one traffic decryption rule configured.

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 vendor-provided patch from Cisco for this vulnerability (CSCvc58563). If a patch is unavailable, consider disabling SSL decryption policies as a temporary workaround or upgrade to an unaffected software release.

Fix this in Secure Firewall Management Center Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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