# CVE-2022-20774: Cisco IP Phone 6800, 7800, and 8800 Series with Multiplatform Firmware Cross-Site Request Forgery Vulnerability

> An attacker can trick an authenticated user into performing configuration changes on Cisco IP Phones, potentially causing a denial of service.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/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:** 6 Apr 2022
- **Updated:** 6 Nov 2024
- **Also known as:** GHSA-xpv7-p5h9-8rgm

## What is CVE-2022-20774?

CVE-2022-20774 is a medium-severity vulnerability in Cisco IP Phone 7800 Series with Multiplatform Firmware, published on 6 Apr 2022. 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 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 configuration changes on the affected device, resulting in a denial of service (DoS) condition.

Weakness: CWE-352 (Cross-Site Request Forgery), CWE-345 (Insufficient Verification of Data Authenticity)

## Which versions are affected by CVE-2022-20774?

It affects 17 products.


Products: Cisco Ip Phone 6825 Firmware, Cisco Ip Phone 6841 Firmware, Cisco Ip Phone 6851 Firmware, Cisco Ip Phone 6861 Firmware, Cisco Ip Phone 6871 Firmware, Cisco Ip Phone 7811 Firmware, Cisco Ip Phone 7821 Firmware, Cisco Ip Phone 7832 Firmware, Cisco Ip Phone 7841 Firmware, Cisco Ip Phone 7861 Firmware, Cisco Ip Phone 8811 Firmware, Cisco Ip Phone 8832 Firmware, Cisco Ip Phone 8841 Firmware, Cisco Ip Phone 8845 Firmware, Cisco Ip Phone 8851 Firmware, Cisco Ip Phone 8861 Firmware, Cisco Ip Phone 8865 Firmware.

## How do I fix CVE-2022-20774?

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

## Is CVE-2022-20774 being exploited?

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

## Other vulnerabilities in Cisco IP Phone 7800 Series with Multiplatform Firmware

- [CVE-2023-20078](https://insights.sbomify.com/CVE-2023-20078/): Cisco IP Phone 6800, 7800, 7900, and 8800 Series Web UI Vulnerabilities (critical 9.8)
- [CVE-2023-20079](https://insights.sbomify.com/CVE-2023-20079/): Cisco IP Phone 6800, 7800, 7900, and 8800 Series Web UI Vulnerabilities (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-20774 and fix it if it is affected.

What it is: CVE-2022-20774 is a medium-severity vulnerability in Cisco IP Phone 7800 Series with Multiplatform Firmware, published on 6 Apr 2022. 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-2022-20774 in the wild and no public exploit code.

Affected product: Cisco IP Phone 7800 Series 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-2022-20774/ (Markdown: https://insights.sbomify.com/CVE-2022-20774/index.md)
```

## Sources

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

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