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

> Remote attackers can cause proxy failures in Sidewinder G2 via invalid traffic, though the system may automatically restart.

- **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:** 20 Nov 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-7j2q-p7jf-5f7p

## What is CVE-2004-2543?

CVE-2004-2543 is a medium-severity denial of service vulnerability in n/a, published on 20 Nov 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Secure Computing Corporation Sidewinder G2 6.1.0.01 might allow remote attackers to cause a denial of service (proxy failure) via invalid traffic to the (1) T.120 or (2) RTSP proxy, or (3) invalid MIME messages to the mail filter.  NOTE: this might not be a vulnerability because the embedded monitoring sub-system automatically restarts after the failure.

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

It affects 1 product.


Products: Securecomputing Sidewinder G2.

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

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

## Is CVE-2004-2543 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2004-2545](https://insights.sbomify.com/CVE-2004-2545/): Denial of service in n/a (medium 5.0)
- [CVE-2004-2399](https://insights.sbomify.com/CVE-2004-2399/): Denial of service in n/a (medium 5.0)
- [CVE-2004-2544](https://insights.sbomify.com/CVE-2004-2544/): Information disclosure in n/a (low 2.1)

## Fix prompt for AI coding agents

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

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

## Sources

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

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