# CVE-2022-20660: Cisco IP Phones Information Disclosure Vulnerability

> An unauthenticated physical attacker can extract confidential information from Cisco IP Phones by accessing unencrypted flash memory chips.

- **Severity:** Medium 4.6 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **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:** 14 Jan 2022
- **Updated:** 6 Nov 2024
- **Also known as:** GHSA-47mp-v7q4-xpjw

## What is CVE-2022-20660?

CVE-2022-20660 is a medium-severity vulnerability in Cisco Session Initiation Protocol (SIP) Software, published on 14 Jan 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability in the information storage architecture of several Cisco IP Phone models could allow an unauthenticated, physical attacker to obtain confidential information from an affected device. This vulnerability is due to unencrypted storage of confidential information on an affected device. An attacker could exploit this vulnerability by physically extracting and accessing one of the flash memory chips. A successful exploit could allow the attacker to obtain confidential information from the device, which could be used for subsequent attacks.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information)

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

It affects 20 products.


Products: Cisco Ip Conference Phone 7832 Firmware, Cisco Ip Conference Phone 8832 Firmware, Cisco Ip Phone 7811 Firmware, Cisco Ip Phone 7821 Firmware, Cisco Ip Phone 7841 Firmware, Cisco Ip Phone 7861 Firmware, Cisco Ip Phone 8811 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, Cisco Unified Ip Conference Phone 8831 Firmware, Cisco Unified Ip Conference Phone 8831 for Third-Party Call Control Firmware, Cisco Unified Ip Phone 7945g Firmware, Cisco Unified Ip Phone 7965g Firmware, Cisco Unified Ip Phone 7975g Firmware, Cisco Unified Sip Phone 3905 Firmware, Cisco Wireless Ip Phone 8821-Ex Firmware, Cisco Wireless Ip Phone 8821 Firmware.

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

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

## Is CVE-2022-20660 being exploited?

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

## Other vulnerabilities in Cisco Session Initiation Protocol (SIP) Software

- [CVE-2020-3111](https://insights.sbomify.com/CVE-2020-3111/): Cisco IP Phone Remote Code Execution and Denial of Service Vulnerability (high 8.8)
- [CVE-2019-1635](https://insights.sbomify.com/CVE-2019-1635/): Cisco IP Phone 7800 Series and 8800 Series Session Initiation Protocol XML Denial of Service Vulnerability (high 7.5)
- [CVE-2021-1379](https://insights.sbomify.com/CVE-2021-1379/): Memory corruption in Cisco IP Phones with Multiplatform Firmware (medium 6.5)
- [CVE-2019-1684](https://insights.sbomify.com/CVE-2019-1684/): Denial of service in Cisco IP Phone 8800 Series Software (medium 6.5)
- [CVE-2021-34711](https://insights.sbomify.com/CVE-2021-34711/): Cisco IP Phone Software Arbitrary File Read Vulnerability (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-20660 is a medium-severity vulnerability in Cisco Session Initiation Protocol (SIP) Software, published on 14 Jan 2022. 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-2022-20660 in the wild and no public exploit code.

Affected product: Cisco Session Initiation Protocol (SIP) Software. 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-20660/ (Markdown: https://insights.sbomify.com/CVE-2022-20660/index.md)
```

## Sources

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

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