# CVE-2017-6625: Denial of service in Cisco Firepower Threat Defense and Cisco ASA with FirePOWER Module

> An authenticated remote attacker can cause a denial of service by sending crafted packets to systems with SSL policy enabled.

- **Severity:** High 7.1 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 May 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-97f5-2h76-3gpr

## What is CVE-2017-6625?

CVE-2017-6625 is a high-severity denial of service vulnerability in Cisco Secure Firewall Threat Defense, published on 3 May 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-399

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

It affects 1 product.


Products: Cisco Secure Firewall Threat Defense.

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

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

## Is CVE-2017-6625 being exploited?

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

## Other vulnerabilities in Cisco Secure Firewall Threat Defense

- [CVE-2024-20412](https://insights.sbomify.com/CVE-2024-20412/): Hardcoded credentials in Cisco Firepower Threat Defense Software (critical 9.3)
- [CVE-2024-20330](https://insights.sbomify.com/CVE-2024-20330/): Memory corruption in Cisco Firepower Threat Defense Software (high 8.6)
- [CVE-2024-20339](https://insights.sbomify.com/CVE-2024-20339/): Cisco Firepower Threat Defense Software for Firepower 2100 Series TLS Denial of Service Vulnerability (high 8.6)
- [CVE-2024-20351](https://insights.sbomify.com/CVE-2024-20351/): Cisco Firepower Threat Defense Software Snort Firewall Denial of Service Vulnerability (high 8.6)
- [CVE-2023-20083](https://insights.sbomify.com/CVE-2023-20083/): Denial of service in Cisco Firepower Threat Defense Software (high 8.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-6625 is a high-severity denial of service vulnerability in Cisco Secure Firewall Threat Defense, published on 3 May 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-6625 in the wild and no public exploit code.

Affected product: Cisco Secure Firewall Threat Defense. 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-6625/ (Markdown: https://insights.sbomify.com/CVE-2017-6625/index.md)
```

## Sources

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

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