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

> Remote attackers can obtain sensitive build information from Novell iChain proxy server HTTP headers without authentication.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Nov 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-8gx2-4pf6-cr9q

## What is CVE-2004-2582?

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

### Official description

Novell iChain 2.3 includes the build number in the VIA line of the proxy server's HTTP headers, which allows remote attackers to obtain sensitive information.

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

It affects 1 product.


Products: Novell Ichain.

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

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

## Is CVE-2004-2582 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-0744](https://insights.sbomify.com/CVE-2005-0744/): Auth bypass in n/a (critical 10.0)
- [CVE-2004-2579](https://insights.sbomify.com/CVE-2004-2579/): Security feature bypass in n/a (high 7.5)
- [CVE-2004-2314](https://insights.sbomify.com/CVE-2004-2314/): Hardcoded credentials in n/a (high 7.5)
- [CVE-2005-0798](https://insights.sbomify.com/CVE-2005-0798/): Auth bypass in n/a (high 7.5)
- [CVE-2003-0636](https://insights.sbomify.com/CVE-2003-0636/): Open redirect in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2004-2582 is a medium-severity vulnerability in n/a, published on 28 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-2582 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-2582/ (Markdown: https://insights.sbomify.com/CVE-2004-2582/index.md)
```

## Sources

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

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