CVE-2009-2556: Buffer Overflow
Published Jul 21, 2009
·Updated
Google Chrome before 2.0.172.37 allows attackers to leverage renderer access to cause a denial of service (memory corruption and application crash) or possibly execute arbitrary code via unspecified vectors that trigger excessive memory allocation.
Affected Software
28 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.172
Google Chrome=2.0.172.30
Google Chrome=2.0.156.1
Google Chrome=1.0.154.46
Google Chrome=0.4.154.22
Google Chrome<=2.0.172.33
Google Chrome=2.0.159.0
Google Chrome=2.0.158.0
Google Chrome=2.0.172.31
Google Chrome=1.0.154.48
Event History
Jul 21, 2009
CVE Published
via MITRE·04:00 PM
Data Sourced
via MITRE·04:00 PM
Description
Frequently Asked Questions
1
What is the severity of CVE-2009-2556?
CVE-2009-2556 has a severity rating that indicates it can lead to denial of service and potential arbitrary code execution.
2
How do I fix CVE-2009-2556?
To fix CVE-2009-2556, users should update Google Chrome to version 2.0.172.37 or later.
3
What types of attacks can exploit CVE-2009-2556?
CVE-2009-2556 can be exploited through memory corruption issues triggered by excessive memory allocation.
4
Which versions of Google Chrome are affected by CVE-2009-2556?
CVE-2009-2556 affects Google Chrome versions prior to 2.0.172.37, including several earlier versions.
5
Can CVE-2009-2556 result in data loss?
Yes, CVE-2009-2556 can lead to application crashes, which may result in data loss.