# CVE-2017-6768: Privilege escalation in Application Policy Infrastructure Controller (APIC)

> An authenticated local attacker can gain root privileges on Cisco APIC devices by exploiting unsafe library loading paths in system executables.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Aug 2017
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-869x-pmmv-pm7c

## What is CVE-2017-6768?

CVE-2017-6768 is a high-severity vulnerability in Cisco Systems, Inc. Application Policy Infrastructure Controller (APIC), published on 17 Aug 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability in the build procedure for certain executable system files installed at boot time on Cisco Application Policy Infrastructure Controller (APIC) devices could allow an authenticated, local attacker to gain root-level privileges. The vulnerability is due to a custom executable system file that was built to use relative search paths for libraries without properly validating the library to be loaded. An attacker could exploit this vulnerability by authenticating to the device and loading a malicious library that can escalate the privilege level. A successful exploit could allow the attacker to gain root-level privileges and take full control of the device. The attacker must have valid user credentials to log in to the device. Cisco Bug IDs: CSCvc96087. Known Affected Releases: 1.1(0.920a), 1.1(1j), 1.1(3f); 1.2 Base, 1.2(2), 1.2(3), 1.2.2; 1.3(1), 1.3(2), 1.3(2f); 2.0 Base, 2.0(1).

Weakness: CWE-426 (Untrusted Search Path)

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

It affects 1 product.


Products: Cisco Application Policy Infrastructure Controller.

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

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

## Is CVE-2017-6768 being exploited?

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

## Other vulnerabilities in Cisco Systems, Inc. Application Policy Infrastructure Controller (APIC)

- [CVE-2021-1393](https://insights.sbomify.com/CVE-2021-1393/): Cisco Application Services Engine Unauthorized Access Vulnerabilities (critical 9.8)
- [CVE-2021-1396](https://insights.sbomify.com/CVE-2021-1396/): Cisco Application Services Engine Unauthorized Access Vulnerabilities (critical 9.8)
- [CVE-2021-1577](https://insights.sbomify.com/CVE-2021-1577/): Cisco Application Policy Infrastructure Controller Arbitrary File Read and Write Vulnerability (critical 9.1)
- [CVE-2023-20011](https://insights.sbomify.com/CVE-2023-20011/): Cross-site request forgery in Cisco Application Policy Infrastructure Controller (APIC) (high 8.8)
- [CVE-2021-1578](https://insights.sbomify.com/CVE-2021-1578/): Cisco Application Policy Infrastructure Controller Privilege Escalation Vulnerability (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-6768 is a high-severity vulnerability in Cisco Systems, Inc. Application Policy Infrastructure Controller (APIC), published on 17 Aug 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-6768 in the wild and no public exploit code.

Affected product: Cisco Systems, Inc. Application Policy Infrastructure Controller (APIC). 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-6768/ (Markdown: https://insights.sbomify.com/CVE-2017-6768/index.md)
```

## Sources

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

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