CVE-2015-1229: net/http/proxy_client_socket.cc in Google Chrome before 41.0.2272.76 does not properly handle a 407 (aka Pr...

Security readout for executives and security teams

CVE-2015-1229 is a Chrome proxy-handling flaw. A malicious proxy server could inject cookies when Chrome received a proxy-authentication response with a Set-Cookie header. Business risk is mainly to users routed through untrusted or compromised proxies on old Chrome versions. Exposure is most plausible on endpoints still running Google Chrome before 41.0.2272.76, especially where traffic uses explicit proxies, captive portals, or centrally managed proxy infrastructure. Current exposure should be rare, but legacy systems, frozen images, or unmanaged lab machines may still matter. Treat this as a legacy hygiene issue unless old Chrome builds remain in use. Prioritize remediation for environments with proxy dependence, shared workstations, or unmanaged endpoints because cookie integrity can affect user sessions and trust boundaries. Mitigation focus: Upgrade Chrome or Chromium to 41.0.2272.76 or later.; Apply relevant Ubuntu, Gentoo, or Red Hat browser security updates where applicable.; Remove or isolate endpoints that cannot run supported browser versions..

Prepared

Jun 14, 2026, 05:11 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.