# CVE-2017-12262: Misconfiguration in Cisco Application Policy Infrastructure Controller Enterprise Module

> Incorrect firewall rules allow adjacent attackers to access internal privileged services on Cisco APIC-EM devices.

- **Severity:** High 8.8 (`CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Nov 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-299r-j638-g338

## What is CVE-2017-12262?

CVE-2017-12262 is a high-severity vulnerability in Cisco Application Policy Infrastructure Controller Enterprise Module, published on 2 Nov 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability within the firewall configuration of the Cisco Application Policy Infrastructure Controller Enterprise Module (APIC-EM) could allow an unauthenticated, adjacent attacker to gain privileged access to services only available on the internal network of the device. The vulnerability is due to an incorrect firewall rule on the device. The misconfiguration could allow traffic sent to the public interface of the device to be forwarded to the internal virtual network of the APIC-EM. An attacker that is logically adjacent to the network on which the public interface of the affected APIC-EM resides could leverage this behavior to gain access to services listening on the internal network with elevated privileges. This vulnerability affects appliances or virtual devices running Cisco Application Policy Infrastructure Controller Enterprise Module prior to version 1.5. Cisco Bug IDs: CSCve89638.

Weakness: CWE-665 (Improper Initialization), CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Cisco Application Policy Infrastructure Controller Enterprise Module.

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

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

## Is CVE-2017-12262 being exploited?

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

## Other vulnerabilities in Cisco Application Policy Infrastructure Controller Enterprise Module

- [CVE-2018-0427](https://insights.sbomify.com/CVE-2018-0427/): Command injection in Digital Network Architecture (DNA) Center (high 8.8)
- [CVE-2016-1365](https://insights.sbomify.com/CVE-2016-1365/): Command injection in n/a (high 8.8)
- [CVE-2018-0368](https://insights.sbomify.com/CVE-2018-0368/): Information disclosure in Cisco Digital Network Architecture Center unknown (high 7.8)
- [CVE-2016-1386](https://insights.sbomify.com/CVE-2016-1386/): Missing authorization in n/a (high 7.5)
- [CVE-2016-1318](https://insights.sbomify.com/CVE-2016-1318/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-12262 is a high-severity vulnerability in Cisco Application Policy Infrastructure Controller Enterprise Module, published on 2 Nov 2017. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-12262 in the wild and no public exploit code.

Affected product: Cisco Application Policy Infrastructure Controller Enterprise Module. 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-12262/ (Markdown: https://insights.sbomify.com/CVE-2017-12262/index.md)
```

## Sources

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

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