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

> Remote attackers can cause a denial of service on Cisco IP Phones by sending a malicious SIP INVITE request with a crafted Remote-Party-ID field.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Mar 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-jf8q-7p9f-qqch

## What is CVE-2007-1542?

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

### Official description

Unspecified vulnerability in the Cisco IP Phone 7940 and 7960 running firmware before POS8-6-0 allows remote attackers to cause a denial of service via the Remote-Party-ID sipURI field in a SIP INVITE request. NOTE: the provenance of this information is unknown; the details are obtained solely from third party information.

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

It affects 2 products.


Products: Cisco 7940 Router, Cisco 7960 Router.

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

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

## Is CVE-2007-1542 being exploited?

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

Public exploit code:

- Cisco Phone 7940/7960 - 'SIP INVITE' Remote Denial of Service (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-1542 is a medium-severity denial of service vulnerability in n/a, published on 20 Mar 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-1542 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-1542/ (Markdown: https://insights.sbomify.com/CVE-2007-1542/index.md)
```

## Sources

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

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