| Summary: | <www-client/chromium-48.0.2564.82: multiple vulnerabilities | ||
|---|---|---|---|
| Product: | Gentoo Security | Reporter: | Agostino Sarubbo <ago> |
| Component: | Vulnerabilities | Assignee: | Gentoo Security <security> |
| Status: | RESOLVED FIXED | ||
| Severity: | major | CC: | chromium |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | http://googlechromereleases.blogspot.com/2016/01/stable-channel-update_20.html | ||
| Whiteboard: | A2 [glsa] | ||
| Package list: | Runtime testing required: | --- | |
chromium-48.0.2564.82 has been added. Please stabilize. amd64 stable (In reply to Richard Freeman from comment #2) > amd64 stable Stable chromium with default "system-ffmpeg" use flag depends on unstable ffmpeg now x86 stable cleanup done (In reply to nE0sIghT from comment #3) > (In reply to Richard Freeman from comment #2) > > amd64 stable > > Stable chromium with default "system-ffmpeg" use flag depends on unstable > ffmpeg now That looks like it should be stable masked. (In reply to nE0sIghT from comment #3) > Stable chromium with default "system-ffmpeg" use flag depends on unstable > ffmpeg now As Rick indicated, it is stable-masked. # Mike Gilbert <floppym@gentoo.org> (02 Dec 2015) # Needs unstable ffmpeg. =www-client/chromium-47* system-ffmpeg =www-client/chromium-48* system-ffmpeg Added to existing GLSA. This issue was resolved and addressed in GLSA 201603-09 at https://security.gentoo.org/glsa/201603-09 by GLSA coordinator Kristian Fiskerstrand (K_F). |
From ${URL} : The Chrome team is delighted to announce the promotion of Chrome 48 to the stable channel for Windows, Mac and Linux. Chrome 48.0.2564.82 contains a number of fixes and improvements -- a list of changes is available in the log. Watch out for upcoming Chrome and Chromium blog posts about new features and big efforts delivered in 48. Security Fixes and Rewards Note: Access to bug details and links may be kept restricted until a majority of users are updated with a fix. We will also retain restrictions if the bug exists in a third party library that other projects similarly depend on, but haven’t yet fixed. This update includes 37 security fixes. Below, we highlight fixes that were contributed by external researchers. Please see the Chromium security page for more information. [$3000][497632] High CVE-2016-1612: Bad cast in V8. Credit to cloudfuzzer. [$3000][572871] High CVE-2016-1613: Use-after-free in PDFium. Credit to anonymous. [$2000][544691] Medium CVE-2016-1614: Information leak in Blink. Credit to Christoph Diehl. [$500][468179] Medium CVE-2016-1615: Origin confusion in Omnibox. Credit to Ron Masas. [$500][541415] Medium CVE-2016-1616: URL Spoofing. Credit to Luan Herrera. [$500][544765] Medium CVE-2016-1617: History sniffing with HSTS and CSP. Credit to jenuis. [$500][552749] Medium CVE-2016-1618: Weak random number generator in Blink. Credit to Aaron Toponce. [$500][557223] Medium CVE-2016-1619: Out-of-bounds read in PDFium. Credit to Keve Nagy. We would also like to thank all security researchers that worked with us during the development cycle to prevent security bugs from ever reaching the stable channel. The total value of additional rewards and their recipients will updated here when all reports have gone through the reward panel. As usual, our ongoing internal security work was responsible for a wide range of fixes: [579625] CVE-2016-1620: Various fixes from internal audits, fuzzing and other initiatives. Multiple vulnerabilities in V8 fixed at the tip of the 4.8 branch (currently 4.8.271.17). @maintainer(s): after the bump, in case we need to stabilize the package, please let us know if it is ready for the stabilization or not.