Advisories ยป MGASA-2017-0111

Updated chromium-browser-stable packages fix security vulnerability

Publication date: 21 Apr 2017
Modification date: 21 Apr 2017
Type: security
Affected Mageia releases : 5
CVE: CVE-2017-5006 , CVE-2017-5007 , CVE-2017-5008 , CVE-2017-5009 , CVE-2017-5010 , CVE-2017-5011 , CVE-2017-5012 , CVE-2017-5013 , CVE-2017-5014 , CVE-2017-5015 , CVE-2017-5016 , CVE-2017-5017 , CVE-2017-5018 , CVE-2017-5019 , CVE-2017-5020 , CVE-2017-5021 , CVE-2017-5022 , CVE-2017-5023 , CVE-2017-5024 , CVE-2017-5025 , CVE-2017-5026 , CVE-2017-5027 , CVE-2017-5029 , CVE-2017-5030 , CVE-2017-5031 , CVE-2017-5032 , CVE-2017-5033 , CVE-2017-5034 , CVE-2017-5035 , CVE-2017-5036 , CVE-2017-5037 , CVE-2017-5038 , CVE-2017-5039 , CVE-2017-5040 , CVE-2017-5041 , CVE-2017-5042 , CVE-2017-5043 , CVE-2017-5044 , CVE-2017-5045 , CVE-2017-5046 , CVE-2017-5052 , CVE-2017-5053 , CVE-2017-5054 , CVE-2017-5055 , CVE-2017-5056

Description

Chromium-browser 57.0.2987.133 fixes security issues:

Multiple flaws were found in the way Chromium 55 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-5006, CVE-2017-5007, CVE-2017-5008,
CVE-2017-5009, CVE-2017-5010, CVE-2017-5011, CVE-2017-5012,
CVE-2017-5013, CVE-2017-5014, CVE-2017-5015, CVE-2017-5016,
CVE-2017-5017, CVE-2017-5018, CVE-2017-5019, CVE-2017-5020,
CVE-2017-5021, CVE-2017-5022, CVE-2017-5023, CVE-2017-5024,
CVE-2017-5025, CVE-2017-5026, CVE-2017-5027, CVE-2017-5029,
CVE-2017-5030, CVE-2017-5031, CVE-2017-5032, CVE-2017-5033,
CVE-2017-5034, CVE-2017-5035, CVE-2017-5036, CVE-2017-5037,
CVE-2017-5038, CVE-2017-5039, CVE-2017-5040, CVE-2017-5041,
CVE-2017-5042, CVE-2017-5043, CVE-2017-5044, CVE-2017-5045,
CVE-2017-5046, CVE-2017-5052, CVE-2017-5053, CVE-2017-5054,
CVE-2017-5055, CVE-2017-5056)

References

SRPMS

5/core