<?xml version="1.0" encoding="UTF-8"?>
<!--PATCHINFO id="b45a97409a57ffb7bfed2096ba136e83"!-->
<patch
    xmlns="http://novell.com/package/metadata/suse/patch"
    xmlns:yum="http://linux.duke.edu/metadata/common"
    xmlns:rpm="http://linux.duke.edu/metadata/rpm"
    xmlns:suse="http://novell.com/package/metadata/suse/common"
    patchid="sdkp3-mozilla-xulrunner190-6617"
    timestamp="1257164092"
    engine="1.0">
  <yum:name>sdkp3-mozilla-xulrunner190</yum:name>
  <summary lang="en">Security update for Mozilla XULRunner</summary>
  <summary lang="de">Security update for Mozilla XULRunner</summary>
  <description lang="en">The Mozilla XULRunner engine was updated to version
1.9.0.15 to fix various bugs and security issues.

Following security issues have been fixed: MFSA 2009-52 /
CVE-2009-3370: Security researcher Paul Stone reported that
a user's form history, both from web content as well as the
smart location bar, was vulnerable to theft. A malicious
web page could synthesize events such as mouse focus and
key presses on behalf of the victim and trick the browser
into auto-filling the form fields with history entries and
then reading the entries.

MFSA 2009-53 / CVE-2009-3274: Security researcher Jeremy
Brown reported that the file naming scheme used for
downloading a file which already exists in the downloads
folder is predictable. If an attacker had local access to a
victim's computer and knew the name of a file the victim
intended to open through the Download Manager, he could use
this vulnerability to place a malicious file in the
world-writable directory used to save temporary downloaded
files and cause the browser to choose the incorrect file
when opening it. Since this attack requires local access to
the victim's machine, the severity of this vulnerability
was determined to be low.

MFSA 2009-54 / CVE-2009-3371: Security researcher Orlando
Berrera of Sec Theory reported that recursive creation of
JavaScript web-workers can be used to create a set of
objects whose memory could be freed prior to their use.
These conditions often result in a crash which could
potentially be used by an attacker to run arbitrary code on
a victim's computer.

MFSA 2009-55 / CVE-2009-3372: Security researcher Marco C.
reported a flaw in the parsing of regular expressions used
in Proxy Auto-configuration (PAC) files. In certain cases
this flaw could be used by an attacker to crash a victim's
browser and run arbitrary code on their computer. Since
this vulnerability requires the victim to have PAC
configured in their environment with specific regular
expresssions which can trigger the crash, the severity of
the issue was determined to be moderate.

MFSA 2009-56 / CVE-2009-3373: Security research firm
iDefense reported that researcher regenrecht discovered a
heap-based buffer overflow in Mozilla's GIF image parser.
This vulnerability could potentially be used by an attacker
to crash a victim's browser and run arbitrary code on their
computer.

MFSA 2009-57 / CVE-2009-3374: Mozilla security researcher
moz_bug_r_a4 reported that the XPCOM utility
XPCVariant::VariantDataToJS unwrapped doubly-wrapped
objects before returning them to chrome callers. This could
result in chrome privileged code calling methods on an
object which had previously been created or modified by web
content, potentially executing malicious JavaScript code
with chrome privileges.


MFSA 2009-59 / CVE-2009-1563: Security researcher Alin Rad
Pop of Secunia Research reported a heap-based buffer
overflow in Mozilla's string to floating point number
conversion routines. Using this vulnerability an attacker
could craft some malicious JavaScript code containing a
very long string to be converted to a floating point number
which would result in improper memory allocation and the
execution of an arbitrary memory location. This
vulnerability could thus be leveraged by the attacker to
run arbitrary code on a victim's computer.

MFSA 2009-61 / CVE-2009-3375: Security researcher Gregory
Fleischer reported that text within a selection on a web
page can be read by JavaScript in a different domain using
the document.getSelection function, violating the
same-origin policy. Since this vulnerability requires user
interaction to exploit, its severity was determined to be
moderate.


MFSA 2009-62 / CVE-2009-3376: Mozilla security researchers
Jesse Ruderman and Sid Stamm reported that when downloading
a file containing a right-to-left override character (RTL)
in the filename, the name displayed in the dialog title bar
conflicts with the name of the file shown in the dialog
body. An attacker could use this vulnerability to obfuscate
the name and file extension of a file to be downloaded and
opened, potentially causing a user to run an executable
file when they expected to open a non-executable file.

MFSA 2009-64 / CVE-2009-3380 / CVE-2009-3381 /
CVE-2009-3382 / CVE-2009-3383: Mozilla developers and
community members identified and fixed several stability
bugs in the browser engine used in Firefox and other
Mozilla-based products. Some of these crashes showed
evidence of memory corruption under certain circumstances
and we presume that with enough effort at least some of
these could be exploited to run arbitrary code.
</description>
  <description lang="de">The Mozilla XULRunner engine was updated to version
1.9.0.15 to fix various bugs and security issues.

Following security issues have been fixed: MFSA 2009-52 /
CVE-2009-3370: Security researcher Paul Stone reported that
a user's form history, both from web content as well as the
smart location bar, was vulnerable to theft. A malicious
web page could synthesize events such as mouse focus and
key presses on behalf of the victim and trick the browser
into auto-filling the form fields with history entries and
then reading the entries.

MFSA 2009-53 / CVE-2009-3274: Security researcher Jeremy
Brown reported that the file naming scheme used for
downloading a file which already exists in the downloads
folder is predictable. If an attacker had local access to a
victim's computer and knew the name of a file the victim
intended to open through the Download Manager, he could use
this vulnerability to place a malicious file in the
world-writable directory used to save temporary downloaded
files and cause the browser to choose the incorrect file
when opening it. Since this attack requires local access to
the victim's machine, the severity of this vulnerability
was determined to be low.

MFSA 2009-54 / CVE-2009-3371: Security researcher Orlando
Berrera of Sec Theory reported that recursive creation of
JavaScript web-workers can be used to create a set of
objects whose memory could be freed prior to their use.
These conditions often result in a crash which could
potentially be used by an attacker to run arbitrary code on
a victim's computer.

MFSA 2009-55 / CVE-2009-3372: Security researcher Marco C.
reported a flaw in the parsing of regular expressions used
in Proxy Auto-configuration (PAC) files. In certain cases
this flaw could be used by an attacker to crash a victim's
browser and run arbitrary code on their computer. Since
this vulnerability requires the victim to have PAC
configured in their environment with specific regular
expresssions which can trigger the crash, the severity of
the issue was determined to be moderate.

MFSA 2009-56 / CVE-2009-3373: Security research firm
iDefense reported that researcher regenrecht discovered a
heap-based buffer overflow in Mozilla's GIF image parser.
This vulnerability could potentially be used by an attacker
to crash a victim's browser and run arbitrary code on their
computer.

MFSA 2009-57 / CVE-2009-3374: Mozilla security researcher
moz_bug_r_a4 reported that the XPCOM utility
XPCVariant::VariantDataToJS unwrapped doubly-wrapped
objects before returning them to chrome callers. This could
result in chrome privileged code calling methods on an
object which had previously been created or modified by web
content, potentially executing malicious JavaScript code
with chrome privileges.


MFSA 2009-59 / CVE-2009-1563: Security researcher Alin Rad
Pop of Secunia Research reported a heap-based buffer
overflow in Mozilla's string to floating point number
conversion routines. Using this vulnerability an attacker
could craft some malicious JavaScript code containing a
very long string to be converted to a floating point number
which would result in improper memory allocation and the
execution of an arbitrary memory location. This
vulnerability could thus be leveraged by the attacker to
run arbitrary code on a victim's computer.

MFSA 2009-61 / CVE-2009-3375: Security researcher Gregory
Fleischer reported that text within a selection on a web
page can be read by JavaScript in a different domain using
the document.getSelection function, violating the
same-origin policy. Since this vulnerability requires user
interaction to exploit, its severity was determined to be
moderate.


MFSA 2009-62 / CVE-2009-3376: Mozilla security researchers
Jesse Ruderman and Sid Stamm reported that when downloading
a file containing a right-to-left override character (RTL)
in the filename, the name displayed in the dialog title bar
conflicts with the name of the file shown in the dialog
body. An attacker could use this vulnerability to obfuscate
the name and file extension of a file to be downloaded and
opened, potentially causing a user to run an executable
file when they expected to open a non-executable file.

MFSA 2009-64 / CVE-2009-3380 / CVE-2009-3381 /
CVE-2009-3382 / CVE-2009-3383: Mozilla developers and
community members identified and fixed several stability
bugs in the browser engine used in Firefox and other
Mozilla-based products. Some of these crashes showed
evidence of memory corruption under certain circumstances
and we presume that with enough effort at least some of
these could be exploited to run arbitrary code.
</description>
  <yum:version ver="6617" rel="0"/>
  <rpm:requires>
    <rpm:entry kind="atom" name="mozilla-xulrunner190-devel" epoch="0" ver="1.9.0.15" rel="0.4.2" flags="EQ"/>
    <rpm:entry kind="atom" name="python-xpcom190" epoch="0" ver="1.9.0.15" rel="0.4.2" flags="EQ"/>
  </rpm:requires>
  <category>security</category>
  <atoms>
    <package xmlns="http://linux.duke.edu/metadata/common" type="rpm">
      <name>mozilla-xulrunner190-devel</name>
      <arch>x86_64</arch>
      <version epoch="0" ver="1.9.0.15" rel="0.4.2"/>
      <checksum type="sha" pkgid="YES">7e6f3c97b11152cd61d1165542eac6e324aa4b33</checksum>
      <time file="1257164337" build="1257164092"/>
      <size package="3190657" installed="25236285" archive="25841308"/>
      <location xml:base="media://#1" href="suse/x86_64/mozilla-xulrunner190-devel-1.9.0.15-0.4.2.x86_64.rpm"/>
      <format>
        <rpm:requires>
          <rpm:entry kind="package" name="mozilla-xulrunner190-devel" epoch="0" ver="1.9.0.15" rel="0.4.2" flags="GE"/>
        </rpm:requires>
        <suse:freshens>
          <suse:entry kind="package" name="mozilla-xulrunner190-devel"/>
        </suse:freshens>
      </format>
      <pkgfiles xmlns="http://novell.com/package/metadata/suse/patch">
      </pkgfiles>
    </package>
    <package xmlns="http://linux.duke.edu/metadata/common" type="rpm">
      <name>python-xpcom190</name>
      <arch>x86_64</arch>
      <version epoch="0" ver="1.9.0.15" rel="0.4.2"/>
      <checksum type="sha" pkgid="YES">32a93157be9687c53afe1b5a4665fc271796f1d1</checksum>
      <time file="1257164337" build="1257164092"/>
      <size package="137635" installed="407196" archive="412320"/>
      <location xml:base="media://#1" href="suse/x86_64/python-xpcom190-1.9.0.15-0.4.2.x86_64.rpm"/>
      <format>
        <rpm:requires>
          <rpm:entry kind="package" name="python-xpcom190" epoch="0" ver="1.9.0.15" rel="0.4.2" flags="GE"/>
        </rpm:requires>
        <suse:freshens>
          <suse:entry kind="package" name="python-xpcom190"/>
        </suse:freshens>
      </format>
      <pkgfiles xmlns="http://novell.com/package/metadata/suse/patch">
      </pkgfiles>
    </package>
  </atoms>
</patch>
