# CVE-2015-4226: Denial of service in n/a

> Remote attackers can cause a denial of service on Cisco 9900 phones by sending malformed RTP packets after a call is answered.

- **Severity:** High 7.1 (`AV:N/AC:M/Au:N/C:N/I:N/A:C`)
- **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:** 30 Jun 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-29v6-j9p2-6qxc

## What is CVE-2015-4226?

CVE-2015-4226 is a high-severity denial of service vulnerability in n/a, published on 30 Jun 2015. 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

The packet-storing feature on Cisco 9900 phones with firmware 9.3(2) does not properly support the RTP protocol, which allows remote attackers to cause a denial of service (device hang) by sending malformed RTP packets after a call is answered, aka Bug ID CSCur39976.

Weakness: CWE-399

## Which versions are affected by CVE-2015-4226?

It affects 1 product.


Products: Cisco Unified Ip Phones 9900 Series Firmware.

## How do I fix CVE-2015-4226?

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

## Is CVE-2015-4226 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-0600](https://insights.sbomify.com/CVE-2015-0600/): Denial of service in n/a (medium 5.0)
- [CVE-2015-0602](https://insights.sbomify.com/CVE-2015-0602/): Information disclosure in n/a (medium 5.0)
- [CVE-2015-0603](https://insights.sbomify.com/CVE-2015-0603/): Misconfiguration in n/a (medium 4.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-4226 and fix it if it is affected.

What it is: CVE-2015-4226 is a high-severity denial of service vulnerability in n/a, published on 30 Jun 2015. 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-2015-4226 in the wild and no public exploit code.

Affected product: n/a. 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-2015-4226/ (Markdown: https://insights.sbomify.com/CVE-2015-4226/index.md)
```

## Sources

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

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