CVE-2005-0175 Other in n/a
Medium 5.0
Published
Updated
Check this codebase for CVE-2005-0175 and fix it if it is affected.
What it is: CVE-2005-0175 is a medium-severity vulnerability in n/a, published on 6 Feb 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-0175 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-0175/ (Markdown: https://insights.sbomify.com/CVE-2005-0175/index.md)
Remote attackers can poison the Squid proxy cache via HTTP response splitting, potentially serving malicious content to users.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2005-0175?
CVE-2005-0175 is a medium-severity vulnerability in n/a, published on 6 Feb 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
Squid 2.5 up to 2.5.STABLE7 allows remote attackers to poison the cache via an HTTP response splitting attack.
Which versions are affected by CVE-2005-0175?
It affects 1 product.
Products include Squid Squid.
How do I fix CVE-2005-0175?
Upgrade to a fixed version.
Is CVE-2005-0175 being exploited?
There is no known exploitation of CVE-2005-0175 in the wild and no public exploit code.
Other vulnerabilities in n/a
Sources
Also known as CVE-2005-1389, DEBIAN-CVE-2005-0175, GHSA-2rv8-xmpq-rpfx.