# CVE-2017-3885: Denial of service in Cisco Firepower Detection Engine

> Remote attackers can cause denial of service in Cisco Firepower by triggering high CPU usage in the SSL reassembly engine when decryption rules are configured.

- **Severity:** Medium 5.9 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Apr 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-96h7-mg93-6889

## What is CVE-2017-3885?

CVE-2017-3885 is a medium-severity denial of service vulnerability in Cisco Secure Firewall Management Center, published on 7 Apr 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2017-3885?

It affects 1 product.


Products: Cisco Secure Firewall Management Center.

## How do I fix CVE-2017-3885?

No fix has been published for CVE-2017-3885 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-3885 being exploited?

There is no known exploitation of CVE-2017-3885 in the wild and no public exploit code.

## Other vulnerabilities in Cisco Secure Firewall Management Center

- [CVE-2026-20079](https://insights.sbomify.com/CVE-2026-20079/): Cisco Firewall Management Center Authentication Bypass Using an Alternate Path or Channel (critical 10.0, exploited in the wild)
- [CVE-2026-20131](https://insights.sbomify.com/CVE-2026-20131/): Cisco Secure Firewall Management Center (FMC) Software and Cisco Security Cloud Control (SCC) Firewall Management Deserialization of Untrusted Data (critical 10.0, exploited in the wild)
- [CVE-2026-20316](https://insights.sbomify.com/CVE-2026-20316/): Cisco Secure Firewall Management Center Use of Hard-coded Password (medium 5.3, exploited in the wild)
- [CVE-2025-20265](https://insights.sbomify.com/CVE-2025-20265/): Cisco Secure Firewall Management Center Software Radius Remote Code Execution Vulnerability (critical 10.0)
- [CVE-2024-20424](https://insights.sbomify.com/CVE-2024-20424/): Command injection in Cisco Firepower Management Center (critical 9.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-3885 and fix it if it is affected.

What it is: CVE-2017-3885 is a medium-severity denial of service vulnerability in Cisco Secure Firewall Management Center, published on 7 Apr 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-3885 in the wild and no public exploit code.

Affected product: Cisco Secure Firewall Management Center. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-3885/ (Markdown: https://insights.sbomify.com/CVE-2017-3885/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-3885
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-3885
- OSV: https://osv.dev/vulnerability/CVE-2017-3885

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-3885/
Summaries are generated and may contain mistakes; the official description above is the record.