Multiple vulnerabilities have been reported in Google Chrome, where some have unknown impacts and others can be exploited by malicious people to bypass certain security restrictions, conduct spoofing attacks, conduct cross-site scripting attacks, and potentially compromise a user's system.

1) An error within the history handling can be exploited to spoof the URL bar and display attacker controlled content while the browser presents the certificate of a trusted site.

2) An error can be exploited to spoof the URL bar by e.g. tricking the user into performing a drag and drop operation on specially crafted content.

3) An error is caused due to the application stripping whitespaces at the end of download filenames.

4) Certain input passed to the appcache internals page is not properly sanitised before being displayed. This can be exploited to execute arbitrary HTML and script code in context of the appcache internals page.

5) A race condition exists within the initialisation of worker processes.

6) An unspecified error can be exploited to redirect to chrome scheme URIs.

7) An unspecified error exists within the HTTP header delimiter handling.

8) Various unspecified errors can be exploited to violate the cross-origin policy.

9) A use-after-free error exists within the media buffer handling.

10) A use-after-free error exists within the counter handling.

11) Various timing issues exist within the DOM traversal.

12) Various issues related to stale styles can lead to use-after-free errors.

13) Unspecified errors within v8 can be exploited to cause out-of-bounds writes.

14) An unspecified error related to javascript URIs can be exploited to steal cookies.

15) A use-after-free error exists related to plug-ins and editing.

16) An error related to Web Audio can be exploited to cause a heap overflow.

17) A use-after-free error exists within the video source handling.

18) Internal v8 functions are exposed.

Solution
Upgrade to version 15.0.874.102.

Provided and/or discovered by
1, 2) Jordi Chancel

The vendor credits:
3) Marc Novak
4) Independently discovered by Google Chrome Security Team (Tom Sepez) and Juho Nurminen
5, 10, 12, 15, 16) miaubiz
6) Masato Kinugawa
7) Vladimir Vorontsov, ONsec company
8, 14) Sergey Glazunov
9) Google Chrome Security Team (Inferno)
11) Brian Ryner, Chromium development community
13) Christian Holler
17) Ami Fischman, Chromium development community
18) Independently discovered by teven Keuchel, Chromium development community and Daniel Divricean

Original Advisory
Google:
http://googlechromereleases.blogspot.com/2011/10/chrome-stable-release.html

Jordi Chancel:
http://www.alternativ-testing.fr/blog/index.php?post/2011/Google-Chrome-URL-Bar-Spoofing-with-SSL-TLS-Spoofing
http://www.alternativ-testing.fr/blog/index.php?post/2011/Google-Chrome-Search-Engine-Location-Bar-URL-Spoofing

Deep Links
Links available to Secunia VIM customers