# CVE-2019-1922: Cisco IP Phone 7800 and 8800 Series Session Initiation Protocol Denial of Service Vulnerability

> Remote attackers can cause Cisco IP phones to reboot and fail registration by sending malformed SIP packets during the registration process.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:H/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:** 6 Jul 2019
- **Updated:** 21 Nov 2024
- **Also known as:** GHSA-996r-f8xw-6h6p

## What is CVE-2019-1922?

CVE-2019-1922 is a medium-severity vulnerability in Cisco IP Phone 8800 Series Software, published on 6 Jul 2019. 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 Cisco SIP IP Phone Software for Cisco IP Phone 7800 Series and 8800 Series could allow an unauthenticated, remote attacker to cause a denial of service (DoS) condition on an affected phone. The vulnerability is due to insufficient validation of input Session Initiation Protocol (SIP) packets. An attacker could exploit this vulnerability by altering the SIP replies that are sent to the affected phone during the registration process. A successful exploit could allow the attacker to cause the phone to reboot and not complete the registration process.

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2019-1922?

It affects 12 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.

## How do I fix CVE-2019-1922?

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

## Is CVE-2019-1922 being exploited?

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

## Other vulnerabilities in Cisco IP Phone 8800 Series 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-2019-1922 and fix it if it is affected.

What it is: CVE-2019-1922 is a medium-severity vulnerability in Cisco IP Phone 8800 Series Software, published on 6 Jul 2019. 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-2019-1922 in the wild and no public exploit code.

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

## Sources

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

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