Advisories » MGASA-2017-0317

Chromium-browser 60.0.3112.101 fixes security issues

Publication date: 28 Aug 2017
Modification date: 28 Aug 2017
Type: security
Affected Mageia releases : 5 , 6
CVE: CVE-2017-5059 , CVE-2017-5060 , CVE-2017-5061 , CVE-2017-5062 , CVE-2017-5063 , CVE-2017-5064 , CVE-2017-5065 , CVE-2017-5066 , CVE-2017-5067 , CVE-2017-5068 , CVE-2017-5069 , CVE-2017-5070 , CVE-2017-5071 , CVE-2017-5072 , CVE-2017-5073 , CVE-2017-5074 , CVE-2017-5075 , CVE-2017-5076 , CVE-2017-5077 , CVE-2017-5078 , CVE-2017-5079 , CVE-2017-5080 , CVE-2017-5081 , CVE-2017-5082 , CVE-2017-5083 , CVE-2017-5085 , CVE-2017-5086 , CVE-2017-5087 , CVE-2017-5088 , CVE-2017-5089 , CVE-2017-5091 , CVE-2017-5092 , CVE-2017-5093 , CVE-2017-5094 , CVE-2017-5095 , CVE-2017-5096 , CVE-2017-5097 , CVE-2017-5098 , CVE-2017-5099 , CVE-2017-5100 , CVE-2017-5101 , CVE-2017-5102 , CVE-2017-5103 , CVE-2017-5104 , CVE-2017-5105 , CVE-2017-5106 , CVE-2017-5107 , CVE-2017-5108 , CVE-2017-5109 , CVE-2017-5110 , CVE-2017-6991

Description

Multiple flaws were found in the way Chromium 57 processes various types
of web content, where loading a web page containing malicious content
could cause Chromium to crash, execute arbitrary code, or disclose
sensitive information. (CVE-2017-5057, CVE-2017-5058, CVE-2017-5059,
CVE-2017-5060, CVE-2017-5061, CVE-2017-5062, CVE-2017-5063,
CVE-2017-5064, CVE-2017-5065, CVE-2017-5066, CVE-2017-5067,
CVE-2017-5068, CVE-2017-5069, CVE-2017-5070, CVE-2017-5071,
CVE-2017-5072, CVE-2017-5073, CVE-2017-5074, CVE-2017-5075,
CVE-2017-5076, CVE-2017-5077, CVE-2017-5078, CVE-2017-5079,
CVE-2017-5080, CVE-2017-5081, CVE-2017-5082, CVE-2017-5083,
CVE-2017-5085, CVE-2017-5086, CVE-2017-5087, CVE-2017-5088,
CVE-2017-5089, CVE-2017-5091, CVE-2017-5092, CVE-2017-5093,
CVE-2017-5094, CVE-2017-5095, CVE-2017-5096, CVE-2017-5097,
CVE-2017-5098, CVE-2017-5099, CVE-2017-5100, CVE-2017-5101,
CVE-2017-5102, CVE-2017-5103, CVE-2017-5104, CVE-2017-5105,
CVE-2017-5106, CVE-2017-5107, CVE-2017-5108, CVE-2017-5109,
CVE-2017-5110, CVE-2017-6991)
                

References

• https://bugs.mageia.org/show_bug.cgi?id=20708
• https://chromereleases.googleblog.com/2017/04/stable-channel-update-for-desktop.html
• https://chromereleases.googleblog.com/2017/05/stable-channel-update-for-desktop.html
• https://chromereleases.googleblog.com/2017/05/stable-channel-update-for-desktop_9.html
• https://chromereleases.googleblog.com/2017/06/stable-channel-update-for-desktop.html
• https://chromereleases.googleblog.com/2017/06/stable-channel-update-for-desktop_15.html
• https://chromereleases.googleblog.com/2017/06/stable-channel-update-for-desktop_20.html
• https://chromereleases.googleblog.com/2017/06/stable-channel-update-for-desktop_26.html
• https://chromereleases.googleblog.com/2017/07/stable-channel-update-for-desktop.html
• https://chromereleases.googleblog.com/2017/08/stable-channel-update-for-desktop.html
• https://chromereleases.googleblog.com/2017/08/stable-channel-update-for-desktop_14.html
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5059
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5060
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5061
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5062
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5063
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5064
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5065
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5066
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5067
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5068
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5069
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5070
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5071
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5072
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5073
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5074
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5075
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5076
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5077
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5078
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5079
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5080
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5081
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5082
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5083
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5085
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5086
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5087
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5088
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5089
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5091
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5092
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5093
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5094
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5095
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5096
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5097
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5098
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5099
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5100
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5101
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5102
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5103
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5104
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5105
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5106
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5107
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5108
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5109
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5110
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-6991

SRPMS

5/core

• chromium-browser-stable-60.0.3112.101-1.mga5
• libwebp-0.4.3-1.1.mga5

6/core

• chromium-browser-stable-60.0.3112.101-1.mga6