# CVE-2024-20279: Cisco Application Policy Infrastructure Controller Unauthorized Policy Actions Vulnerability

> Authenticated attackers in restricted security domains can modify default system policies, disrupting network traffic across all tenants.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **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:** 28 Aug 2024
- **Updated:** 28 Aug 2024
- **Also known as:** GHSA-wxwr-gxwh-c78c

## What is CVE-2024-20279?

CVE-2024-20279 is a medium-severity missing authorization vulnerability in Cisco Application Policy Infrastructure Controller (APIC), published on 28 Aug 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability in the restricted security domain implementation of Cisco Application Policy Infrastructure Controller (APIC) could allow an authenticated, remote attacker to modify the behavior of default system policies, such as quality of service (QoS) policies, on an affected system. This vulnerability is due to improper access control when restricted security domains are used to implement multi-tenancy. An attacker with a valid user account associated with a restricted security domain could exploit this vulnerability. A successful exploit could allow the attacker to read, modify, or delete child policies created under default system policies, which are implicitly used by all tenants in the fabric, resulting in disruption of network traffic. Exploitation is not possible for policies under tenants that an attacker has no authorization to access.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2024-20279?

It affects 1 product.


Products: Cisco Application Policy Infrastructure Controller.

## How do I fix CVE-2024-20279?

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

## Is CVE-2024-20279 being exploited?

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

## Other vulnerabilities in Cisco 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-2024-20279 and fix it if it is affected.

What it is: CVE-2024-20279 is a medium-severity missing authorization vulnerability in Cisco Application Policy Infrastructure Controller (APIC), published on 28 Aug 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-20279 in the wild and no public exploit code.

Affected product: Cisco 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-2024-20279/ (Markdown: https://insights.sbomify.com/CVE-2024-20279/index.md)
```

## Sources

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

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