Hello community,

here is the log from the commit of package patchinfo.5579 for 
openSUSE:13.2:Update checked in at 2016-09-13 10:04:55
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:13.2:Update/patchinfo.5579 (Old)
 and      /work/SRC/openSUSE:13.2:Update/.patchinfo.5579.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "patchinfo.5579"

Changes:
--------
New Changes file:

NO CHANGES FILE!!!

New:
----
  _patchinfo

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Other differences:
------------------
++++++ _patchinfo ++++++
<patchinfo incident="5579">
  <packager>AndreasStieger</packager>
  <issue tracker="bnc" id="996032">openSUSE Tumbleweed 20160826: Chromium 
crashes systematically when loading certain web pages</issue>
  <issue tracker="bnc" id="99606">Changing GCVs on Driverset properties doesnt 
dirty the model</issue>
  <issue tracker="bnc" id="995932">Chromium 52 crashes when trying to open 
page</issue>
  <issue tracker="bnc" id="996648">VUL-0: chromium: multiple vulnerabilities 
fixed in 53.0.2785.89</issue>
  <issue tracker="cve" id="2016-5147"></issue>
  <issue tracker="cve" id="2016-5148"></issue>
  <issue tracker="cve" id="2016-5149"></issue>
  <issue tracker="cve" id="2016-5150"></issue>
  <issue tracker="cve" id="2016-5151"></issue>
  <issue tracker="cve" id="2016-5152"></issue>
  <issue tracker="cve" id="2016-5153"></issue>
  <issue tracker="cve" id="2016-5154"></issue>
  <issue tracker="cve" id="2016-5155"></issue>
  <issue tracker="cve" id="2016-5156"></issue>
  <issue tracker="cve" id="2016-5157"></issue>
  <issue tracker="cve" id="2016-5158"></issue>
  <issue tracker="cve" id="2016-5159"></issue>
  <issue tracker="cve" id="2016-5160"></issue>
  <issue tracker="cve" id="2016-5161"></issue>
  <issue tracker="cve" id="2016-5162"></issue>
  <issue tracker="cve" id="2016-5163"></issue>
  <issue tracker="cve" id="2016-5164"></issue>
  <issue tracker="cve" id="2016-5165"></issue>
  <issue tracker="cve" id="2016-5166"></issue>
  <issue tracker="bnc" id="969732">rpmlint fails with MemoryError (on 32bit 
builds)</issue>
  <issue tracker="bnc" id="998328"></issue>
  <category>security</category>
  <rating>important</rating>
  <summary>Security update for Chromium</summary>
  <description>Chromium was updated to 53.0.2785.101 to fix a number of 
security issues and bugs.

The following vulnerabilities were fixed: (boo#996648)

- CVE-2016-5147: Universal XSS in Blink.
- CVE-2016-5148: Universal XSS in Blink.
- CVE-2016-5149: Script injection in extensions.
- CVE-2016-5150: Use after free in Blink.
- CVE-2016-5151: Use after free in PDFium.
- CVE-2016-5152: Heap overflow in PDFium.
- CVE-2016-5153: Use after destruction in Blink.
- CVE-2016-5154: Heap overflow in PDFium.
- CVE-2016-5155: Address bar spoofing.
- CVE-2016-5156: Use after free in event bindings.
- CVE-2016-5157: Heap overflow in PDFium.
- CVE-2016-5158: Heap overflow in PDFium.
- CVE-2016-5159: Heap overflow in PDFium.
- CVE-2016-5161: Type confusion in Blink.
- CVE-2016-5162: Extensions web accessible resources bypass.
- CVE-2016-5163: Address bar spoofing.
- CVE-2016-5164: Universal XSS using DevTools.
- CVE-2016-5165: Script injection in DevTools.
- CVE-2016-5166: SMB Relay Attack via Save Page As.
- CVE-2016-5160: Extensions web accessible resources bypass.
 
The following upstream fixes are included:

- SPDY crasher fixes
- Disable NV12 DXGI video on AMD
- Forward --password-store switch to os_crypt
- Tell the kernel to discard USB requests when they time out.
- disallow WKBackForwardListItem navigations for pushState pages
- arc: bluetooth: Fix advertised uuid
- fix conflicting PendingIntent for stop button and swipe away

A number of tracked build system fixes are included. (boo#996032, boo#99606, 
boo#995932)

The following tracked regression fix is included: - Re-enable widevine plugin 
(boo#998328)

rpmlint and rpmlint-mini were updated to work around a memory exhaustion 
problem with this package on 32 bit (boo#969732).</description>
</patchinfo>

Reply via email to