# CVE-2004-0945: Denial of service in n/a

> Authenticated remote attackers can cause denial of service on Mitel 3300 ICP by exhausting resources with excessive active sessions.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Feb 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-v47j-qgrw-jfmf

## What is CVE-2004-0945?

CVE-2004-0945 is a medium-severity denial of service vulnerability in n/a, published on 28 Feb 2005. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The web management interface for Mitel 3300 Integrated Communications Platform (ICP) before 4.2.2.11 allows remote authenticated users to cause a denial of service (resource exhaustion) via a large number of active sessions, which exceeds ICP's maximum.

## Which versions are affected by CVE-2004-0945?

It affects 1 product.


Products: Mitel Mitel 3300 Integrated Communication Platform.

## How do I fix CVE-2004-0945?

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

## Is CVE-2004-0945 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-0945 and fix it if it is affected.

What it is: CVE-2004-0945 is a medium-severity denial of service vulnerability in n/a, published on 28 Feb 2005. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2004-0945 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-2004-0945/ (Markdown: https://insights.sbomify.com/CVE-2004-0945/index.md)
```

## Sources

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

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