
| South Carolina Information Sharing and Analysis Center |
SC INFORMATION SHARING AND ANALYSIS CENTER BULLETIN
DATE ISSUED: 2/22/2013
SUBJECT: Multiple Google Chrome Vulnerabilities Could Allow for Remote Code Execution
OVERVIEW:
Multiple vulnerabilities have been discovered in Google Chrome that could allow remote code execution, the bypass of security restrictions, or cause denial-of-service conditions. Google Chrome is a web browser used to access the Internet. Details are not currently available that depict accurate attack scenarios, but it is believed that some of the vulnerabilities can likely be exploited if a user visits, or is redirected to a specially crafted web page.
Successful exploitation of these vulnerabilities may result in either an attacker gaining the same privileges as the logged on user, or gaining session authentication credentials. Depending on the privileges associated with the user, an attacker could install programs; view, change, or delete data; or create new accounts with full user rights.
DESCRIPTION:
Multiple vulnerabilities have been discovered in Google Chrome, Details of these vulnerabilities are as follows:
- A memory-corruption with web audio nodes.
- A use-after-free error exists in database handling.
- A security issue that occurs due to a bad read in Matroska handling.
- A security issue due to bad memory access with excessive SVG parameters.
- A security issue due to a bad read in Skia.
- A security issue due to an inappropriate load of NaCl.
- A security issue because too many API permissions are granted to the web store.
- A security issue exists due to incorrect NaCl signal handling.
- A security issue occurs because the developer tools process has too many permissions and places too much trust in the connected server.
- An out-of-bounds read issue in Skia.
- A security issue that occurs due to a tighten user gesture check for dangerous file downloads.
- Multiple memory-corruption issues exist across the IPC layer.
- An integer-overflow vulnerability occurs when handling blob.
- Multiple security weakness exist across the IPC layer.
- A race-condition vulnerability occurs when handling media.
- A buffer-overflow vulnerability exists in vorbis decoding.
- A security issue exist due to incorrect path handling while copying a file.
- Multiple security issues occurs due to memory management when handling a plug-in message.
- An off-by-one read issue exists in PDF.
- A use-after-free issue occurs when handling a URL.
- An integer-overflow vulnerability occurs when handling Opus.
- A race-condition vulnerability exists in ICU.
Successful exploitation of some of the above vulnerabilities could result in an attacker gaining the same privileges as the user. Depending on the privileges associated with the user, an attacker could install programs; view, change, delete data; or create new accounts with full user rights. Failed exploit attempts will likely cause denial-of-service conditions.
SYSTEM AFFECTED:
- Google Chrome for Windows and Linux versions prior to 25.0.1364.97
- Google Chrome for Mac versions prior to 25.0.1364.99
RISK:
Government:
Large and medium government entities: High
Small government entities: High
Businesses:
Large and medium business entities: High
Small business entities: High
Home users: High
RECOMMENDATIONS:
We recommend the following actions be taken:
· Update vulnerable Google Chrome products immediately after appropriate testing by following the steps outlined by Google here:
http://support.google.com/chrome/bin/answer.py?hl=en&answer=95414
· Run all software as a non-privileged user (one without administrative privileges) to diminish the effects of a successful attack.
· Remind users not to visit un-trusted websites, follow links, or open files provided by unknown or un-trusted sources.
REFERENCES:
Security Focus:
http://www.securityfocus.com/bid/58101
CVE:
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-0879
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-0880
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-0881
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-0882
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-0883
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-0884
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-0885
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-0886
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-0887
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-0888
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-0889
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-0890
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-0891
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-0892
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-0893
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-0894
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-0895
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-0896
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-0897
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-0898
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-0899
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-0900
Please feel free to contact the SC ISAC if you have any questions or need any additional information.
The SC ISAC will provide amplifying information as it becomes available.
SC-ISAC Contact Information
Email: SC-ISAC@cio.sc.gov
SC ISAC Security Line: 803-896-1650
24-hour hotline: +1 803-896-0001 Option 2
Fax: +1 803-896-0375
Postal address:
SC-ISAC
DSIT Budget and Control Board
4430 Broad River Road
Columbia S.C. 29210
SC-ISAC is available via hotline 08:00-17:00 EST (GMT-5)/ EDT (GMT-4)
Monday through Friday
Using Encryption
We strongly urge you to encrypt sensitive information sent by email. Our
public PGP key is available from:
https://sc-isac.sc.gov/public.key
NO WARRANTY
Any material furnished by SC-ISAC is furnished on an "as is" basis.
SC-ISAC makes no warranties of any kind, either expressed or implied as to
any matter including, but not limited to, warranty of fitness for a particular
purpose or merchantability, exclusivity or results obtained from use of the
material. SC-ISAC does not make any warranty of any kind with respect to
freedom from patent, trademark, or copyright infringement.