# CVE-2018-0243: Security feature bypass in Cisco Firepower System Software

> An attacker can bypass malware detection policies to transfer malicious SMB2/SMB3 files through Cisco Firepower devices configured with file action policies.

- **Severity:** Medium 5.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Apr 2018
- **Updated:** 29 Nov 2024
- **Also known as:** GHSA-522c-wx8c-28p2

## What is CVE-2018-0243?

CVE-2018-0243 is a medium-severity vulnerability in Cisco Secure Firewall Threat Defense, published on 19 Apr 2018. 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 of Cisco Firepower System Software could allow an unauthenticated, remote attacker to bypass a configured file action policy that is intended to drop the Server Message Block Version 2 (SMB2) and SMB Version 3 (SMB3) protocols if malware is detected. The vulnerability is due to incorrect detection of an SMB2 or SMB3 file based on the total file length. An attacker could exploit this vulnerability by sending a crafted SMB2 or SMB3 transfer request through the targeted device. An exploit could allow the attacker to pass SMB2 or SMB3 files that could be malware even though the device is configured to block them. This vulnerability does not exist for SMB Version 1 (SMB1) files. This vulnerability affects Cisco Firepower System Software when one or more file action policies are configured, on software releases prior to 6.2.3. Cisco Bug IDs: CSCvg68807.

Weakness: CWE-693 (Protection Mechanism Failure)

## Which versions are affected by CVE-2018-0243?

It affects 1 product.


Products: Cisco Secure Firewall Threat Defense.

## How do I fix CVE-2018-0243?

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

## Is CVE-2018-0243 being exploited?

There is no known exploitation of CVE-2018-0243 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-2018-0243 and fix it if it is affected.

What it is: CVE-2018-0243 is a medium-severity vulnerability in Cisco Secure Firewall Threat Defense, published on 19 Apr 2018. 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-2018-0243 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-2018-0243/ (Markdown: https://insights.sbomify.com/CVE-2018-0243/index.md)
```

## Sources

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

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