Hello community,

here is the log from the commit of package patchinfo.1675 for 
openSUSE:12.3:Update checked in at 2013-05-27 16:06:08
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:12.3:Update/patchinfo.1675 (Old)
 and      /work/SRC/openSUSE:12.3:Update/.patchinfo.1675.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "patchinfo.1675"

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

NO CHANGES FILE!!!

New:
----
  _patchinfo

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

Other differences:
------------------
++++++ _patchinfo ++++++
<patchinfo>
  <issue id="819204" tracker="bnc">VUL-0: Mozilla 21/17.0.6 security 
release</issue>
  <issue id="CVE-2013-1675" tracker="cve" />
  <issue id="CVE-2013-1674" tracker="cve" />
  <issue id="CVE-2013-1677" tracker="cve" />
  <issue id="CVE-2013-1676" tracker="cve" />
  <issue id="CVE-2013-1670" tracker="cve" />
  <issue id="CVE-2013-1680" tracker="cve" />
  <issue id="CVE-2013-1681" tracker="cve" />
  <issue id="CVE-2013-1679" tracker="cve" />
  <issue id="CVE-2013-1678" tracker="cve" />
  <issue id="CVE-2013-1669" tracker="cve" />
  <issue id="CVE-2013-0801" tracker="cve" />
  <category>security</category>
  <rating>important</rating>
  <packager>wrosenauer</packager>
  <description>Mozilla xulrunner was updated to 17.0.6esr (bnc#819204)
  * MFSA 2013-41/CVE-2013-0801/CVE-2013-1669
    Miscellaneous memory safety hazards
  * MFSA 2013-42/CVE-2013-1670 (bmo#853709)
    Privileged access for content level constructor
  * MFSA 2013-46/CVE-2013-1674 (bmo#860971)
    Use-after-free with video and onresize event
  * MFSA 2013-47/CVE-2013-1675 (bmo#866825)
    Uninitialized functions in DOMSVGZoomEvent
  * MFSA 2013-48/CVE-2013-1676/CVE-2013-1677/CVE-2013-1678/
    CVE-2013-1679/CVE-2013-1680/CVE-2013-1681
    Memory corruption found using Address Sanitizer
</description>
  <summary>xulrunner: security update to 17.0.6esr</summary>
</patchinfo>
-- 
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to