dbcve.org
Secure Firewall Threat DefenseApplication · Cisco

CVE-2017-3887

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 that handles 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 unexpectedly restarts. This vulnerability affects Cisco Firepower System Software prior to the first fixed release when it is configured with an SSL Decrypt-Resign policy. More Information: CSCvb62292. Known Affected Releases: 6.0.1 6.1.0 6.2.0. Known Fixed Releases: 6.2.0 6.1.0.2.

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 Cisco Firepower's SSL detection engine allows an unauthenticated remote attacker to cause a denial of service by sending specially crafted SSL packets that crash and restart the Snort intrusion detection process. This only affects systems configured with an SSL Decrypt-Resign policy, which is used for SSL/TLS interception and inspection.

MitigationUpgrade Cisco Firepower System Software to version 6.1.0.2 or 6.2.0 or later. If immediate upgrade is not feasible, consider disabling the SSL Decrypt-Resign policy if SSL inspection is not mission-critical, though this reduces security monitoring 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.1= 6.1.0= 6.2.0

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
    Run 'show version' or access the Firepower Management Center to confirm the device is Cisco Firepower Threat Defense (FTD)
    Affected if The device is not Cisco Firepower Threat Defense (this CVE only affects FTD)
  2. Determine the software version
    Run 'show version' or check the Firepower Management Center console for the exact software version number
    Affected if The version is exactly 6.0.1, 6.1.0, or 6.2.0
  3. Locate SSL inspection policies
    Access the Firepower Management Center under Policies > SSL Inspection or use CLI to list SSL policies configured on the device
    Affected if No SSL inspection policies exist, the check does not apply
  4. Check for SSL Decrypt-Resign policy
    Examine the SSL inspection policy configuration to determine if a Decrypt-Resign rule is active. In CLI this may appear as 'show ssl-policy' or access the policy via the web interface under SSL Settings
    Affected if An SSL Decrypt-Resign policy is enabled and actively intercepting SSL/TLS traffic
  5. Confirm Snort process status
    Run 'show module' or 'system support status' to verify the Snort process is running and hasn't recently crashed or restarted unexpectedly
    Affected if Snort process shows recent crashes or unexpected restarts in logs

You are affected only if you run Firepower Threat Defense versions 6.0.1, 6.1.0, or 6.2.0 AND have an active SSL Decrypt-Resign policy configured for SSL/TLS interception.

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 version 6.1.0.2 or 6.2.0 or later. If immediate upgrade is not feasible, consider disabling the SSL Decrypt-Resign policy if SSL inspection is not mission-critical, though this reduces security monitoring capabilities.

Fix this in Secure Firewall Threat Defense Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,590
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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