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

> Remote attackers can cause denial of service on Aastra SIP phones by sending malicious SDP headers, disrupting call reception.

- **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:** 27 Jun 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-vjpf-ph39-5hrp

## What is CVE-2007-3441?

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

### Official description

Format string vulnerability in the Aastra 9112i SIP Phone with firmware 1.4.0.1048 and boot version 1.1.0.10 allows remote attackers to cause a denial of service (blocked call reception and slow calling) via format string specifiers in an SDP header value, a different vulnerability than CVE-2007-3349.

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

It affects 1 product.


Products: Aastra Telecom 9112i Sip Phone.

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

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

## Is CVE-2007-3441 being exploited?

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

## Other vulnerabilities in n/a

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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