ChromeWeb browser · Google
CVE-2009-2060
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedsrc/net/http/http_transaction_winhttp.cc in Google Chrome before 1.0.154.53 uses the HTTP Host header to determine the context of a document provided in a (1) 4xx or (2) 5xx CONNECT response from a proxy server, which allows man-in-the-middle attackers to execute arbitrary web script by modifying this CONNECT response, aka an "SSL tampering" attack.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceGoogle Chrome before 1.0.154.53 incorrectly uses the HTTP Host header from proxy server 4xx/5xx CONNECT responses to determine document context, allowing MITM attackers to inject arbitrary web script via modified CONNECT responses. This is an SSL tampering attack exploiting improper validation of proxy error responses.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
ChromeWeb browser
<= 1.0.154.52= 0.2.149.29= 0.2.149.30= 0.2.152.1= 0.2.153.1= 0.3.154.0= 0.3.154.3= 0.4.154.18= 0.4.154.22= 0.4.154.31= 0.4.154.33= 1.0.154.36CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- None
AV:N/AC:M/Au:N/C:P/I:P/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed Chrome versionNavigate to chrome://version or about:version in the Chrome address bar and note the version number displayedAffected if The version is 1.0.154.52 or earlier, or matches any of these specific versions: 0.2.149.29, 0.2.149.30, 0.2.152.1, 0.2.153.1, 0.3.154.0, 0.3.154.3, 0.4.154.18, 0.4.154.22, 0.4.154.31, 0.4.154.33, or 1.0.154.36
-
Verify proxy configurationNavigate to Chrome Settings > Advanced > System > Open your computer's proxy settings (or chrome://net-internals/#proxy on older versions) to check if an HTTP/HTTPS proxy is configuredAffected if A manual proxy configuration is enabled and pointing to a proxy server that handles CONNECT requests for SSL/TLS traffic
-
Confirm CONNECT method usageIf a proxy is configured, any SSL/TLS connections to external sites will use the HTTP CONNECT method, which triggers the vulnerable code path when proxy returns 4xx/5xx errorsAffected if Proxy is configured and actively used for HTTPS connections, making the Host header validation flaw exploitable
You are affected if your Chrome version is 1.0.154.52 or earlier (or one of the listed specific vulnerable versions) AND you have a proxy configured that handles HTTPS connections via the CONNECT method.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataEnsure proper validation of document context in proxy error responses rather than trusting the Host header; verify SSL/TLS integrity independently of HTTP-level headers. Update to Chrome 1.0.154.53 or later.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,056.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2009-2060 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2009-2060 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data