MGASA-2017-0317

See a problem?
Please try reporting it to the source first.
Source
https://advisories.mageia.org/MGASA-2017-0317.html
Import Source
https://advisories.mageia.org/MGASA-2017-0317.json
JSON Data
https://api.osv.dev/v1/vulns/MGASA-2017-0317
Upstream
  • 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
Published
2017-08-28T22:48:03Z
Modified
2026-04-16T06:26:15.768358656Z
Summary
Chromium-browser 60.0.3112.101 fixes security issues
Details

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
Credits

Affected packages

Mageia:5 / chromium-browser-stable

Package

Name
chromium-browser-stable
Purl
pkg:rpm/mageia/chromium-browser-stable?arch=source&distro=mageia-5

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
60.0.3112.101-1.mga5

Ecosystem specific 

{
    "section": "core"
}

Database specific

source 
"https://advisories.mageia.org/MGASA-2017-0317.json"

Mageia:5 / libwebp

Package

Name
libwebp
Purl
pkg:rpm/mageia/libwebp?arch=source&distro=mageia-5

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
0.4.3-1.1.mga5

Ecosystem specific 

{
    "section": "core"
}

Database specific

source 
"https://advisories.mageia.org/MGASA-2017-0317.json"

Mageia:6 / chromium-browser-stable

Package

Name
chromium-browser-stable
Purl
pkg:rpm/mageia/chromium-browser-stable?arch=source&distro=mageia-6

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
60.0.3112.101-1.mga6

Ecosystem specific 

{
    "section": "core"
}

Database specific

source 
"https://advisories.mageia.org/MGASA-2017-0317.json"