# CVE-2004-2544: Information disclosure in n/a

> Attackers with admin access can export private keys from firewall certificates, leading to sensitive information disclosure.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Nov 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-r8q3-xj3m-hq8q

## What is CVE-2004-2544?

CVE-2004-2544 is a low-severity vulnerability in n/a, published on 20 Nov 2005. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Admin Console in Secure Computing Corporation Sidewinder G2 6.1.0.01 exports private keys when exporting firewall certificates, which might allow attackers to obtain sensitive information.

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

It affects 1 product.


Products: Securecomputing Sidewinder G2.

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

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

## Is CVE-2004-2544 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2004-2543](https://insights.sbomify.com/CVE-2004-2543/): Denial of service in n/a (medium 5.0)
- [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)

## Fix prompt for AI coding agents

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

What it is: CVE-2004-2544 is a low-severity vulnerability in n/a, published on 20 Nov 2005. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2004-2544 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-2544/ (Markdown: https://insights.sbomify.com/CVE-2004-2544/index.md)
```

## Sources

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

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