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

> Remote attackers can cause device inoperability on Nokia N95 phones by sending a specific sequence of 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:** 15 Dec 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-m67q-3h3c-73p4

## What is CVE-2007-6371?

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

### Official description

Nokia N95 cell phone with RM-159 12.0.013 firmware allows remote attackers to cause a denial of service (device inoperability) via a SIP INVITE message accompanied by an immediately subsequent SIP CANCEL message, followed by a second SIP INVITE message in a different session.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Nokia N95.

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

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

## Is CVE-2007-6371 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-0649](https://insights.sbomify.com/CVE-2009-0649/): Denial of service in n/a (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-6371 is a high-severity denial of service vulnerability in n/a, published on 15 Dec 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-6371 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-2007-6371/ (Markdown: https://insights.sbomify.com/CVE-2007-6371/index.md)
```

## Sources

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

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