# CVE-2007-4459: Denial of service in n/a

> Remote attackers can cause a denial of service and device reboot on Cisco IP Phones by sending specific sequences of invalid SIP messages.

- **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:** Not needed
- **Fix available:** No
- **Published:** 21 Aug 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-r3r7-8q5v-779v

## What is CVE-2007-4459?

CVE-2007-4459 is a high-severity denial of service vulnerability in n/a, published on 21 Aug 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Cisco IP Phone 7940 and 7960 with P0S3-08-6-00 firmware, and other SIP firmware before 8.7(0), allows remote attackers to cause a denial of service (device reboot) via (1) a certain sequence of 10 invalid SIP INVITE and OPTIONS messages; or (2) a certain invalid SIP INVITE message that contains a remote tag, followed by a certain set of two related SIP OPTIONS messages.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2007-4459?

It affects 2 products.


Products: Cisco Voip Phone Cp-7940, Cisco Voip Phone Cp-7960.

## How do I fix CVE-2007-4459?

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

## Is CVE-2007-4459 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-4459 exists.

Public exploit code:

- Cisco IP Phone 7940 - 3 SIP Messages Remote Denial of Service (exploitdb)
- Cisco IP Phone 7940 - 10 SIP Messages Remote Denial of Service (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-4459 and fix it if it is affected.

What it is: CVE-2007-4459 is a high-severity denial of service vulnerability in n/a, published on 21 Aug 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-4459 exists.

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-2007-4459/ (Markdown: https://insights.sbomify.com/CVE-2007-4459/index.md)
```

## Sources

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

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