CVE-2009-0801
Squid HTTP Host Header Spoofing Vulnerability
Description
Squid, when transparent interception mode is enabled, uses the HTTP Host header to determine the remote endpoint, which allows remote attackers to bypass access controls for Flash, Java, Silverlight, and probably other technologies, and possibly communicate with restricted intranet sites, via a crafted web page that causes a client to send HTTP requests with a modified Host header.
INFO
Published Date :
March 4, 2009, 4:30 p.m.
Last Modified :
April 9, 2025, 12:30 a.m.
Source :
[email protected]
Remotely Exploitable :
Yes !
Impact Score :
6.9
Exploitability Score :
4.9
Public PoC/Exploit Available at Github
CVE-2009-0801 has a 8 public PoC/Exploit available at Github.
Go to the Public Exploits tab to see the list.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2009-0801.
| URL | Resource |
|---|---|
| http://www.kb.cert.org/vuls/id/435052 | Third Party Advisory US Government Resource |
| http://www.securityfocus.com/bid/33858 | |
| http://www.kb.cert.org/vuls/id/435052 | Third Party Advisory US Government Resource |
| http://www.securityfocus.com/bid/33858 |
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Caching proxy for developers
cache caching go golang
Just Go
None
Makefile C Shell Python Dockerfile
None
Makefile C Shell Python Dockerfile
redsocks
Makefile C Shell Python Dockerfile
Using Toolchain: https://github.com/SuzukiHonoka/Padavan_Toolchain3.4.x_EXTRA to build.
Makefile C Shell Python Dockerfile
Run Squid on a Docker container. The main purpose of this it to use it as Docker registry cache.
Shell
None
Python
transparent TCP-to-proxy redirector
C Makefile Shell Python Dockerfile
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2009-0801 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2009-0801 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Modified by af854a3a-2127-422b-91ae-364da2661108
Nov. 21, 2024
Action Type Old Value New Value Added Reference http://www.kb.cert.org/vuls/id/435052 Added Reference http://www.securityfocus.com/bid/33858 -
CVE Modified by [email protected]
May. 14, 2024
Action Type Old Value New Value -
Initial Analysis by [email protected]
Mar. 04, 2009
Action Type Old Value New Value
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2009-0801 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2009-0801
weaknesses.
Exploit Prediction
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days.
0.05 }} 0.02%
score
0.16316
percentile