# CVE-2025-20158: Cisco Video Phone 8875 and Desk Phone 9800 Series Information Disclosure Vulnerability

> An authenticated local attacker with SSH access can exploit a debug shell flaw to read sensitive information from Cisco IP phones.

- **Severity:** Medium 4.4 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Feb 2025
- **Updated:** 19 Feb 2025
- **Also known as:** GHSA-fppv-gxpq-7mg9

## What is CVE-2025-20158?

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

### Official description

A vulnerability in the debug shell of Cisco Video Phone 8875 and Cisco Desk Phone 9800 Series could allow an authenticated, local attacker to access sensitive information on an affected device. To exploit this vulnerability, the attacker must have valid administrative credentials with SSH access on the affected device. SSH access is disabled by default.

This vulnerability is due to insufficient validation of user-supplied input by the debug shell of an affected device. An attacker could exploit this vulnerability by sending a crafted SSH client command to the CLI. A successful exploit could allow the attacker to access sensitive information on the underlying operating system.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2025-20158?

It affects 5 products.


Products: Cisco Desk Phone 9841 Firmware, Cisco Desk Phone 9851 Firmware, Cisco Desk Phone 9861 Firmware, Cisco Desk Phone 9871 Firmware, Cisco Video Phone 8875 Firmware.

## How do I fix CVE-2025-20158?

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

## Is CVE-2025-20158 being exploited?

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

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

- [CVE-2025-20350](https://insights.sbomify.com/CVE-2025-20350/): Memory corruption in Cisco Session Initiation Protocol (SIP) Software (high 7.5)
- [CVE-2025-20351](https://insights.sbomify.com/CVE-2025-20351/): Cross-site scripting in Cisco Session Initiation Protocol (SIP) Software (medium 6.1)
- [CVE-2025-20335](https://insights.sbomify.com/CVE-2025-20335/): Missing authorization in Cisco Session Initiation Protocol (SIP) Software (medium 5.3)
- [CVE-2025-20336](https://insights.sbomify.com/CVE-2025-20336/): Information disclosure in Cisco Session Initiation Protocol (SIP) Software (medium 5.3)
- [CVE-2024-20445](https://insights.sbomify.com/CVE-2024-20445/): Cisco IP Phone 7800, 8800, and 9800 Series Information Disclosure Vulnerability (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-20158 and fix it if it is affected.

What it is: CVE-2025-20158 is a medium-severity vulnerability in Cisco Session Initiation Protocol (SIP) Software, published on 19 Feb 2025. 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-2025-20158 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-2025-20158/ (Markdown: https://insights.sbomify.com/CVE-2025-20158/index.md)
```

## Sources

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

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