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

> Remote attackers can cause a denial of service in APC PowerChute Business Edition via unknown vectors.

- **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 stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 May 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-jg52-mx67-ggv2

## What is CVE-2004-2046?

CVE-2004-2046 is a medium-severity denial of service vulnerability in n/a, published on 10 May 2005. It can be exploited over the network, with no action from the victim.

### Official description

Unknown vulnerability in APC PowerChute Business Edition 6.0 through 7.0.1 allows remote attackers to cause a denial of service via unknown attack vectors.

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

It affects 1 product.


Products: Apc Powerchute.

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

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

## Is CVE-2004-2046 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2000-1242](https://insights.sbomify.com/CVE-2000-1242/): Hardcoded credentials in n/a (critical 9.0)
- [CVE-2020-7526](https://insights.sbomify.com/CVE-2020-7526/): Code injection in PowerChute Business Edition software V9.0.x and earlier (high 8.8)
- [CVE-2002-1924](https://insights.sbomify.com/CVE-2002-1924/): Misconfiguration in n/a (medium 5.0)
- [CVE-2011-4263](https://insights.sbomify.com/CVE-2011-4263/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

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

## Sources

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

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