CVE-2009-2121: Buffer Overflow
Published Jun 23, 2009
·Updated
Buffer overflow in the browser kernel in Google Chrome before 2.0.172.33 allows remote HTTP servers to cause a denial of service (application crash) or possibly execute arbitrary code via a crafted response.
Affected Software
24 affected components
Google Chrome=0.3.154.3
Google Chrome=0.2.149.30
Google Chrome=0.4.154.31
Google Chrome=1.0.154.39
Google Chrome=1.0.154.59
Google Chrome=1.0.154.53
Google Chrome=0.4.154.33
Google Chrome=1.0.154.43
Google Chrome=1.0.154.42
Google Chrome=1.0.154.52
Google Chrome=2.0.157.2
Google Chrome=0.4.154.18
Google Chrome=0.2.149.29
Google Chrome=2.0.157.0
Google Chrome=0.2.152.1
Google Chrome=0.3.154.0
Google Chrome=0.2.153.1
Google Chrome=1.0.154.36
Google Chrome=2.0.156.1
Google Chrome=1.0.154.46
Google Chrome=0.4.154.22
Google Chrome=2.0.159.0
Google Chrome=2.0.158.0
Google Chrome<=2.0.172
Event History
Jun 23, 2009
CVE Published
via MITRE·09:21 PM
Data Sourced
via MITRE·09:21 PM
Description
Frequently Asked Questions
1
What is the severity of CVE-2009-2121?
CVE-2009-2121 has a high severity rating due to its potential to cause application crashes or allow arbitrary code execution.
2
How do I fix CVE-2009-2121?
To fix CVE-2009-2121, upgrade Google Chrome to version 2.0.172.34 or later.
3
What versions of Google Chrome are affected by CVE-2009-2121?
CVE-2009-2121 affects Google Chrome versions before 2.0.172.34, including 0.2.x and 1.0.x versions.
4
What are the potential impacts of CVE-2009-2121?
The potential impacts of CVE-2009-2121 include denial of service from application crashes and possible remote code execution.
5
Is there a workaround for CVE-2009-2121?
There is no known workaround for CVE-2009-2121; the best mitigation is to update Google Chrome to a patched version.