# CVE-2006-5233: Denial of service in n/a

> Remote attackers can cause a denial of service reboot on Polycom SoundPoint IP phones by sending long URLs to the HTTP daemon.

- **Severity:** High 7.8 (`AV:N/AC:L/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:** 11 Oct 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-q2wc-rv5p-5hv3

## What is CVE-2006-5233?

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

### Official description

Polycom SoundPoint IP 301 VoIP Desktop Phone, firmware version 1.4.1.0040, allows remote attackers to cause a denial of service (reboot) via (1) a long URL sent to the HTTP daemon and (2) unspecified manipulations as demonstrated by the Nessus http_fingerprinting_hmap.nasl script.

## Which versions are affected by CVE-2006-5233?

It affects 1 product.


Products: Polycom Soundpoint Ip 301.

## How do I fix CVE-2006-5233?

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

## Is CVE-2006-5233 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-5233 and fix it if it is affected.

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

## Sources

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

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