CVE-2009-1836: Medium severity Mozilla SeaMonkey vulnerability
Microsoft security researchers Shuo Chen, Ziqing Mao, Yi-Min Wang, and Ming Zhang reported that when a CONNECT request is sent to a proxy server and a non-200 response is returned, then the body of the response is incorrectly rendered within the context of the request Host: header. An active network attacker could use this vulnerability to intercept a CONNECT request and reply with a non-200 response containing malicious code which would be executed within the context of the victim's requested SSL-protected domain. Since this attack requires the victim to have a proxy configured, the severity of this issue was determined to be high.
Other sources
Mozilla Firefox before 3.0.11, Thunderbird before 2.0.0.22, and SeaMonkey before 1.1.17 use the HTTP Host header to determine the context of a document provided in a non-200 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.
Affected Software
Remediation
Patch Available
Patch Available
Event History
Frequently Asked Questions
What is the severity of CVE-2009-1836?
CVE-2009-1836 has a severity rating that varies depending on the affected application, but it is generally considered to pose a significant risk.
How do I fix CVE-2009-1836?
To fix CVE-2009-1836, users should update their affected applications to the latest versions provided by Mozilla.
Which software versions are affected by CVE-2009-1836?
CVE-2009-1836 affects various versions of Mozilla SeaMonkey, Firefox, and Thunderbird, particularly those listed in the vulnerability report.
What types of attacks can exploit CVE-2009-1836?
CVE-2009-1836 can be exploited by attackers through crafted CONNECT requests sent to a proxy server.
Is there a workaround for CVE-2009-1836?
While the best solution is to update software, temporarily avoiding the use of proxy servers may reduce exposure to CVE-2009-1836.