# CVE-2017-12299: Security feature bypass in Cisco ASA Next-Generation Firewall Services

> Unauthenticated remote attackers can bypass local IP management traffic filters on Cisco ASA firewalls to access restricted services.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/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:** 16 Nov 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-mm54-9jw6-25g6

## What is CVE-2017-12299?

CVE-2017-12299 is a medium-severity vulnerability in Cisco Firepower Extensible Operating System, published on 16 Nov 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability exists in the process of creating default IP blocks during device initialization for Cisco ASA Next-Generation Firewall Services that could allow an unauthenticated, remote attacker to send traffic to the local IP address of the device, bypassing any filters that are configured to deny local IP management traffic. The vulnerability is due to an implementation error that exists in the process of creating default IP blocks when the device is initialized, and the way in which those IP blocks interact with user-configured filters for local IP management traffic (for example, SSH to the device). An attacker could exploit this vulnerability by sending traffic to the local IP address of the targeted device. A successful exploit could allow the attacker to connect to the local IP address of the device even when there are filters configured to deny the traffic. Cisco Bug IDs: CSCvd97962.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Cisco Firepower Extensible Operating System.

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

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

## Is CVE-2017-12299 being exploited?

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

## Other vulnerabilities in Cisco Firepower Extensible Operating System

- [CVE-2018-0310](https://insights.sbomify.com/CVE-2018-0310/): Information disclosure in Cisco FXOS and NX-OS unknown (critical 9.8)
- [CVE-2015-6435](https://insights.sbomify.com/CVE-2015-6435/): Command injection in n/a (critical 9.8)
- [CVE-2021-1368](https://insights.sbomify.com/CVE-2021-1368/): Memory corruption in Cisco NX-OS Software (high 8.8)
- [CVE-2020-3456](https://insights.sbomify.com/CVE-2020-3456/): Cisco FXOS Software Firepower Chassis Manager Cross-Site Request Forgery Vulnerability (high 8.8)
- [CVE-2020-3172](https://insights.sbomify.com/CVE-2020-3172/): Cisco FXOS and NX-OS Software Cisco Discovery Protocol Arbitrary Code Execution and Denial of Service Vulnerability (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-12299 is a medium-severity vulnerability in Cisco Firepower Extensible Operating System, published on 16 Nov 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-12299 in the wild and no public exploit code.

Affected product: Cisco Firepower Extensible Operating System. 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-12299/ (Markdown: https://insights.sbomify.com/CVE-2017-12299/index.md)
```

## Sources

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

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