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

> Remote attackers can obtain sensitive information from Squid Web Proxy Cache by triggering DNS failures with invalid hostnames, exposing previous error messages.

- **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:** Yes
- **Published:** 21 Aug 2005
- **Updated:** 8 Aug 2024
- **Also known as:** DEBIAN-CVE-2004-2479, GHSA-wf7x-gjvh-m5r3

## What is CVE-2004-2479?

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

### Official description

Squid Web Proxy Cache 2.5 might allow remote attackers to obtain sensitive information via URLs containing invalid hostnames that cause DNS operations to fail, which results in references to previously used error messages.

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

It affects 1 product.


Products: National Science Foundation Squid Web Proxy Cache.

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

Upgrade to a fixed version.

## Is CVE-2004-2479 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2004-0541](https://insights.sbomify.com/CVE-2004-0541/): Memory corruption in n/a (critical 10.0)
- [CVE-2004-2480](https://insights.sbomify.com/CVE-2004-2480/): Security feature bypass in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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