# CVE-2009-3704: Denial of service in n/a

> Remote attackers can crash the ZoIPer softphone by sending a SIP INVITE request with an empty Call-Info header.

- **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:** 16 Oct 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-gf9w-mffq-c45p

## What is CVE-2009-3704?

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

### Official description

ZoIPer 2.22, and possibly other versions before 2.24 Library 5324, allows remote attackers to cause a denial of service (crash) via a SIP INVITE request with an empty Call-Info header.

## Which versions are affected by CVE-2009-3704?

It affects 1 product.


Products: Zoiper Zoiper.

## How do I fix CVE-2009-3704?

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

## Is CVE-2009-3704 being exploited?

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

Public exploit code:

- ZoIPer 2.22 - Call-Info Remote Denial of Service (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-3704 and fix it if it is affected.

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

## Sources

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

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