# CVE-2005-0095: Denial of service in n/a

> Remote attackers can crash the Squid proxy server by sending malformed WCCP messages with spoofed source addresses.

- **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:** Yes
- **Published:** 19 Jan 2005
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2005-0095, GHSA-f5hx-2mw6-fpj8

## What is CVE-2005-0095?

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

### Official description

The WCCP message parsing code in Squid 2.5.STABLE7 and earlier allows remote attackers to cause a denial of service (crash) via malformed WCCP messages with source addresses that are spoofed to reference Squid's home router and invalid WCCP_I_SEE_YOU cache numbers.

## Which versions are affected by CVE-2005-0095?

It affects 1 product.


Products: Squid Squid.

## How do I fix CVE-2005-0095?

Upgrade to a fixed version.

## Is CVE-2005-0095 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-0194](https://insights.sbomify.com/CVE-2005-0194/): Auth bypass in n/a (critical 10.0)
- [CVE-2005-1345](https://insights.sbomify.com/CVE-2005-1345/): Missing authorization in n/a (high 7.5)
- [CVE-2005-0173](https://insights.sbomify.com/CVE-2005-0173/): Auth bypass in n/a (high 7.5)
- [CVE-2004-0189](https://insights.sbomify.com/CVE-2004-0189/): Security feature bypass in n/a (high 7.5)
- [CVE-2002-0163](https://insights.sbomify.com/CVE-2002-0163/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-0095 and fix it if it is affected.

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

## Sources

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

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