SB2011051601 - Multiple vulnerabilities in Techland Chrome
Published: May 16, 2011 Updated: August 11, 2020
Breakdown by Severity
- Low
- Medium
- High
- Critical
Description
This security bulletin contains information about 5 secuirty vulnerabilities.
1) Input validation error (CVE-ID: CVE-2011-1804)
The vulnerability allows a remote non-authenticated attacker to read and manipulate data.
rendering/RenderBox.cpp in WebCore in WebKit before r86862, as used in Google Chrome before 11.0.696.71, does not properly render floats, which allows remote attackers to cause a denial of service or possibly have unspecified other impact via unknown vectors that lead to a "stale pointer."
2) Buffer overflow (CVE-ID: CVE-2011-1806)
The vulnerability allows a remote non-authenticated attacker to execute arbitrary code.
Google Chrome before 11.0.696.71 does not properly implement the GPU command buffer, which allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via unspecified vectors.
3) Out-of-bounds write (CVE-ID: CVE-2011-1807)
The vulnerability allows a remote non-authenticated attacker to execute arbitrary code.
Google Chrome before 11.0.696.71 does not properly handle blobs, which allows remote attackers to execute arbitrary code via unspecified vectors that trigger an out-of-bounds write.
4) Input validation error (CVE-ID: CVE-2011-1801)
The vulnerability allows a remote non-authenticated attacker to manipulate data.
Unspecified vulnerability in Google Chrome before 11.0.696.71 allows remote attackers to bypass the pop-up blocker via unknown vectors.
5) Integer overflow (CVE-ID: CVE-2011-1800)
The vulnerability allows a remote non-authenticated attacker to read and manipulate data.
Multiple integer overflows in the SVG Filters implementation in WebCore in WebKit in Google Chrome before 11.0.696.68 allow remote attackers to cause a denial of service or possibly have unspecified other impact via unknown vectors.
Remediation
Install update from vendor's website.
References
- http://code.google.com/p/chromium/issues/detail?id=82546
- http://codereview.chromium.org/7050016
- http://googlechromereleases.blogspot.com/2011/05/stable-channel-update_24.html
- http://trac.webkit.org/changeset/86862
- http://www.securityfocus.com/bid/47965
- https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A13992
- http://code.google.com/p/chromium/issues/detail?id=82873
- http://www.securityfocus.com/bid/47964
- https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A14389
- http://code.google.com/p/chromium/issues/detail?id=82903
- http://www.securityfocus.com/bid/47963
- https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A14471
- http://code.google.com/p/chromium/issues/detail?id=72189
- http://www.securityfocus.com/bid/47966
- https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A14474
- http://code.google.com/p/chromium/issues/detail?id=80608
- http://codereview.chromium.org/6949013
- http://googlechromereleases.blogspot.com/2011/05/stable-channel-update.html
- http://trac.webkit.org/changeset/85996
- https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A14187