# CVE-2023-20221: Cross-site request forgery in Cisco IP Phones with Multiplatform Firmware

> Unauthenticated remote attackers can force a factory reset via CSRF, causing denial of service on Cisco IP Phones.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 Aug 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-rqx3-xf8g-6759

## What is CVE-2023-20221?

CVE-2023-20221 is a medium-severity vulnerability in Cisco IP Phones with Multiplatform Firmware, published on 16 Aug 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A vulnerability in the web-based management interface of Cisco IP Phone 6800, 7800, and 8800 Series with Multiplatform Firmware could allow an unauthenticated, remote attacker to conduct a cross-site request forgery (CSRF) attack against a user of the web-based management interface of an affected system.

 This vulnerability is due to insufficient CSRF protections for the web-based management interface of an affected device. An attacker could exploit this vulnerability by persuading an authenticated user of the interface to follow a crafted link. A successful exploit could allow the attacker to perform a factory reset of the affected device, resulting in a Denial of Service (DoS) condition.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2023-20221?

It affects 23 products.


Products: Cisco Ip Conference Phone 7832 With Multiplatform Firmware, Cisco Ip Conference Phone 8831 With Multiplatform Firmware, Cisco Ip Conference Phone 8832 With Multiplatform Firmware, Cisco Ip Phone 6821 With Multiplatform Firmware, Cisco Ip Phone 6825 With Multiplatform Firmware, Cisco Ip Phone 6841 With Multiplatform Firmware, Cisco Ip Phone 6851 With Multiplatform Firmware, Cisco Ip Phone 6861 With Multiplatform Firmware, Cisco Ip Phone 6871 With Multiplatform Firmware, Cisco Ip Phone 7811 With Multiplatform Firmware, Cisco Ip Phone 7821 With Multiplatform Firmware, Cisco Ip Phone 7841 With Multiplatform Firmware, Cisco Ip Phone 7861 With Multiplatform Firmware, Cisco Ip Phone 8800 Key Expansion Module With Multiplatform Firmware, Cisco Ip Phone 8811 With Multiplatform Firmware, Cisco Ip Phone 8841 With Multiplatform Firmware, Cisco Ip Phone 8845 With Multiplatform Firmware, Cisco Ip Phone 8851 Key Expansion Module With Multiplatform Firmware, Cisco Ip Phone 8851 With Multiplatform Firmware, Cisco Ip Phone 8861 Key Expansion Module With Multiplatform Firmware and 3 more.

## How do I fix CVE-2023-20221?

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

## Is CVE-2023-20221 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-20221 and fix it if it is affected.

What it is: CVE-2023-20221 is a medium-severity vulnerability in Cisco IP Phones with Multiplatform Firmware, published on 16 Aug 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-20221 in the wild and no public exploit code.

Affected product: Cisco IP Phones with Multiplatform Firmware. 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-2023-20221/ (Markdown: https://insights.sbomify.com/CVE-2023-20221/index.md)
```

## Sources

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

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