MGASA-2016-0279: chromium-browser-stable Mageia
Published
Published 09-08-2016Last modified 16-04-2026
Vulnerability summary
MGASA-2016-0279 is a vulnerability in chromium-browser-stable Mageia with no CVSS score yet.
Priority
Insufficient evidence
No CVSS vector published; no exploitation reported by the 5 checked sources
Source freshness unavailable
How is this decided?CVSS score
Not scored
010
No CVSS score recordedEPSS scoreNot scoredRisk metrics not yet published.
KEVNot listedNot listed by any tracked catalog.
RansomwareNot flaggedNo ransomware use recorded.
Public exploits0No public exploits recorded
Advisory lineage
Upstream 8 · Downstream 0Timeline
- 09-08-2016PublishedVulnerability first disclosed.
- 16-04-2026Last modifiedVulnerability information updated.
Description
Updated chromium-browser-stable packages fix security vulnerability Chromium-browser-stable 52.0.2743.116 fixes security issues: two heap overflow issues in pdfium (CVE-2016-5139 and CVE-2016-5140); an address bar spoofing problem (CVE-2016-5141); a use-after-free bug (CVE-2016-5142) and a same origin bypass problem (CVE-2016-5145) in blink; two parameter sanitization failures in DevTools (CVE-2016-5143 and CVE-2016-5144); and various fixes from upstream's internal audits, fuzzing, and other initiatives (CVE-2016-5146).
CVSS metrics
Risk metrics not yet published.
EPSS trend
No EPSS score has been published for this record yet.
Known exploited
Compare KEV catalogs
CISA KEVNot in the CISA KEV catalog.
ENISA CNWNot in the ENISA CNW catalog.
CIRCLNot in the CIRCL catalog.
Public exploits
0 foundNo public exploits indexed.
Weaknesses
CWE · root causeNo weakness data has been published for this record.
Affected systems
Version check
Known conditions: not stated in public data.
Mageia1 product
- chromium-browser-stable< 52.0.2743.116-1.mga5
1 vendor · 1 product
References
3 linksRelated vulnerabilities
Insufficient evidenceMGASA-2017-0317mageia · chromium-browser-stable +2 moremageia chromium-browser-stableChromium-browser 60.0.3112.101 fixes security issues
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)CVSSUnscoredInsufficient evidenceMGASA-2017-0111mageia · chromium-browser-stablemageia chromium-browser-stableUpdated chromium-browser-stable packages fix security vulnerability
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)CVSSUnscoredInsufficient evidenceMGASA-2016-0419mageia · chromium-browser-stablemageia chromium-browser-stableUpdated chromium-browser-stable packages fix security vulnerabilities
Multiple flaws were found in the way Chromium 54 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-2016-5203, CVE-2016-5204, CVE-2016-5205, CVE-2016-5206,
CVE-2016-5207, CVE-2016-5208, CVE-2016-5209, CVE-2016-5210, CVE-2016-5211,
CVE-2016-5212, CVE-2016-5213, CVE-2016-5214, CVE-2016-5215, CVE-2016-5216,
CVE-2016-5217, CVE-2016-5218, CVE-2016-5219, CVE-2016-5220, CVE-2016-5221,
CVE-2016-5222, CVE-2016-5223, CVE-2016-5224, CVE-2016-5225, CVE-2016-5226,
CVE-2016-9650, CVE-2016-9651, CVE-2016-9652)CVSSUnscoredInsufficient evidenceMGASA-2016-0403mageia · chromium-browser-stablemageia chromium-browser-stableUpdated chromium-browser-stable packages fix security vulnerabilities
Multiple flaws were found in Chromium's processing of web content where
loading a web page containing malicious content could cause Chromium to
crash, execute arbitrary code, or disclose sensitive information.
(CVE-2016-5181, CVE-2016-5182, CVE-2016-5183, CVE-2016-5184,
CVE-2016-5185, CVE-2016-5186, CVE-2016-5187, CVE-2016-5188,
CVE-2016-5189, CVE-2016-5190, CVE-2016-5191, CVE-2016-5192,
CVE-2016-5193, CVE-2016-5194, CVE-2016-5198, CVE-2016-5199,
CVE-2016-5200, CVE-2016-5201, CVE-2016-5202)CVSSUnscoredInsufficient evidenceMGASA-2016-0335mageia · chromium-browser-stablemageia chromium-browser-stableUpdated chromium-browser-stable packages fix security vulnerability
Chromium-browser-stable 53.0.2785.143 provides fixes for security issues:
a use-after-free bug in V8 (CVE-2016-5177) and various problems found in
upstream's internal audits, fuzzing, and other initiatives
(CVE-2016-5178).CVSSUnscoredInsufficient evidenceMGASA-2016-0309mageia · chromium-browser-stablemageia chromium-browser-stableUpdated chromium-browser-stable packages fix security vulnerability
Blink, as used in Chromium before 53.0.2785.89 on Windows and OS X and
before 53.0.2785.92 on Linux, mishandles deferred page loads, which
allows remote attackers to inject arbitrary web script or HTML via a
crafted web site, aka "Universal XSS (UXSS)." (CVE-2016-5147)
Cross-site scripting (XSS) vulnerability in Blink, as used in Chromium
before 53.0.2785.89 on Windows and OS X and before 53.0.2785.92 on
Linux, allows remote attackers to inject arbitrary web script or HTML
via vectors related to widget updates, aka "Universal XSS (UXSS)."
(CVE-2016-5148)
The extensions subsystem in Chromium before 53.0.2785.89 on Windows and
OS X and before 53.0.2785.92 on Linux relies on an IFRAME source URL to
identify an associated extension, which allows remote attackers to
conduct extension-bindings injection attacks by leveraging script access
to a resource that initially has the about:blank URL. (CVE-2016-5149)
WebKit/Source/bindings/modules/v8/V8BindingForModules.cpp in Blink, as
used in Chromium before 53.0.2785.89 on Windows and OS X and before
53.0.2785.92 on Linux, has an Indexed Database (aka IndexedDB) API
implementation that does not properly restrict key-path evaluation,
which allows remote attackers to cause a denial of service
(use-after-free) or possibly have unspecified other impact via crafted
JavaScript code that leverages certain side effects. (CVE-2016-5150)
PDFium in Chromium before 53.0.2785.89 on Windows and OS X and before
53.0.2785.92 on Linux mishandles timers, which allows remote attackers
to cause a denial of service (use-after-free) or possibly have
unspecified other impact via a crafted PDF document, related to
fpdfsdk/javascript/JS_Object.cpp and fpdfsdk/javascript/app.cpp.
(CVE-2016-5151)
Integer overflow in the opj_tcd_get_decoded_tile_size function in tcd.c
in OpenJPEG, as used in PDFium in Chromium before 53.0.2785.89 on
Windows and OS X and before 53.0.2785.92 on Linux, allows remote
attackers to cause a denial of service (heap-based buffer overflow) or
possibly have unspecified other impact via crafted JPEG 2000 data.
(CVE-2016-5152)
The Web Animations implementation in Blink, as used in Chromium before
53.0.2785.89 on Windows and OS X and before 53.0.2785.92 on Linux,
improperly relies on list iteration, which allows remote attackers to
cause a denial of service (use-after-destruction) or possibly have
unspecified other impact via a crafted web site. (CVE-2016-5153)
Multiple heap-based buffer overflows in PDFium, as used in Chromium
before 53.0.2785.89 on Windows and OS X and before 53.0.2785.92 on
Linux, allow remote attackers to cause a denial of service or possibly
have unspecified other impact via a crafted JBig2 image. (CVE-2016-5154)
Chromium before 53.0.2785.89 on Windows and OS X and before 53.0.2785.92
on Linux does not properly validate access to the initial document,
which allows remote attackers to spoof the address bar via a crafted web
site. (CVE-2016-5155)
extensions/renderer/event_bindings.cc in the event bindings in Chromium
before 53.0.2785.89 on Windows and OS X and before 53.0.2785.92 on Linux
attempts to process filtered events after failure to add an event
matcher, which allows remote attackers to cause a denial of service
(use-after-free) or possibly have unspecified other impact via unknown
vectors. (CVE-2016-5156)
Heap-based buffer overflow in the opj_dwt_interleave_v function in dwt.c
in OpenJPEG, as used in PDFium in Chromium before 53.0.2785.89 on
Windows and OS X and before 53.0.2785.92 on Linux, allows remote
attackers to execute arbitrary code via crafted coordinate values in
JPEG 2000 data. (CVE-2016-5157)
Multiple integer overflows in the opj_tcd_init_tile function in tcd.c in
OpenJPEG, as used in PDFium in Chromium before 53.0.2785.89 on Windows
and OS X and before 53.0.2785.92 on Linux, allow remote attackers to
cause a denial of service (heap-based buffer overflow) or possibly have
unspecified other impact via crafted JPEG 2000 data. (CVE-2016-5158)
Multiple integer overflows in OpenJPEG, as used in PDFium in Chromium
before 53.0.2785.89 on Windows and OS X and before 53.0.2785.92 on
Linux, allow remote attackers to cause a denial of service (heap-based
buffer overflow) or possibly have unspecified other impact via crafted
JPEG 2000 data that is mishandled during opj_aligned_malloc calls in
dwt.c and t1.c. (CVE-2016-5159)
The AllowCrossRendererResourceLoad function in
extensions/browser/url_request_util.cc in Chromium before 53.0.2785.89
on Windows and OS X and before 53.0.2785.92 on Linux does not properly
use an extension's manifest.json web_accessible_resources field for
restrictions on IFRAME elements, which makes it easier for remote
attackers to conduct clickjacking attacks, and trick users into changing
extension settings, via a crafted web site, a different vulnerability
than CVE-2016-5162. (CVE-2016-5160)
The EditingStyle::mergeStyle function in
WebKit/Source/core/editing/EditingStyle.cpp in Blink, as used in
Chromium before 53.0.2785.89 on Windows and OS X and before 53.0.2785.92
on Linux, mishandles custom properties, which allows remote attackers to
cause a denial of service or possibly have unspecified other impact via
a crafted web site that leverages "type confusion" in the
StylePropertySerializer class. (CVE-2016-5161)
The AllowCrossRendererResourceLoad function in
extensions/browser/url_request_util.cc in Chromium before 53.0.2785.89
on Windows and OS X and before 53.0.2785.92 on Linux does not properly
use an extension's manifest.json web_accessible_resources field for
restrictions on IFRAME elements, which makes it easier for remote
attackers to conduct clickjacking attacks, and trick users into changing
extension settings, via a crafted web site, a different vulnerability
than CVE-2016-5160. (CVE-2016-5162)
The bidirectional-text implementation in Chromium before 53.0.2785.89 on
Windows and OS X and before 53.0.2785.92 on Linux does not ensure
left-to-right (LTR) rendering of URLs, which allows remote attackers to
spoof the address bar via crafted right-to-left (RTL) Unicode text,
related to omnibox/SuggestionView.java and omnibox/UrlBar.java in Chrome
for Android. (CVE-2016-5163)
Cross-site scripting (XSS) vulnerability in
WebKit/Source/platform/v8_inspector/V8Debugger.cpp in Blink, as used in
Chromium before 53.0.2785.89 on Windows and OS X and before 53.0.2785.92
on Linux, allows remote attackers to inject arbitrary web script or HTML
into the Developer Tools (aka DevTools) subsystem via a crafted web
site, aka "Universal XSS (UXSS)." (CVE-2016-5164)
Cross-site scripting (XSS) vulnerability in the Developer Tools (aka
DevTools) subsystem in Chromium before 53.0.2785.89 on Windows and OS X
and before 53.0.2785.92 on Linux allows remote attackers to inject
arbitrary web script or HTML via the settings parameter in a
chrome-devtools-frontend.appspot.com URL's query string. (CVE-2016-5165)
The download implementation in Chromium before 53.0.2785.89 on Windows
and OS X and before 53.0.2785.92 on Linux does not properly restrict
saving a file:// URL that is referenced by an http:// URL, which makes
it easier for user-assisted remote attackers to discover NetNTLM hashes
and conduct SMB relay attacks via a crafted web page that is accessed
with the "Save page as" menu choice. (CVE-2016-5166)
Multiple unspecified vulnerabilities in Chromium before 53.0.2785.89 on
Windows and OS X and before 53.0.2785.92 on Linux allow attackers to
cause a denial of service or possibly have other impact via unknown
vectors. (CVE-2016-5167)
WebKit/Source/bindings/modules/v8/V8BindingForModules.cpp in Blink, as
used in Chromium before 53.0.2785.113, has an Indexed Database (aka
IndexedDB) API implementation that inspects properties not owned by the
array when converting an array to a key, resulting in side effects and a
potential use-after-free problem. (CVE-2016-5170)
Blink, as used in Chromium before 53.0.2785.113, allowed its
WindowProperties constructor to be called from javascript, resulting in
a potential use-after-free problem. (CVE-2016-5171)
Chromium before 53.0.2785.113 exhibits three more separate issues:
arbitrary Memory Read in v8 (CVE-2016-5172), extension resource access
(CVE-2016-5173), and a pop-up event was not correctly suppressed
(CVE-2016-5174).
Finally, Chromium 53.0.2785.113 contains (as usual) various fixes from
upstream's internal audits, fuzzing and other initiatives.
(CVE-2016-5175)CVSSUnscored