-----BEGIN PGP SIGNED MESSAGE-----

______________________________________________________________________________

                        SUSE Security Announcement

        Package:                XFree86-server,xorg-x11-server
        Announcement ID:        SUSE-SA:2005:056
        Date:                   Mon, 26 Sep 2005 14:00:00 +0000
        Affected Products:      SUSE LINUX 9.0, 9.1, 9.2, 9.3
                                SUSE Linux Desktop 1.0
                                SUSE Linux Enterprise Server 8, 9
                                Novell Linux Desktop 9
        Vulnerability Type:     remote command execution
        Severity (1-10):        9
        SUSE Default Package:   yes
        Cross-References:       CAN-2005-2495

    Content of This Advisory:
        1) Security Vulnerability Resolved:
             pixmap integer overflow
           Problem Description
        2) Solution or Work-Around
        3) Special Instructions and Notes
        4) Package Location and Checksums
        5) Pending Vulnerabilities, Solutions, and Work-Arounds:
            none
        6) Authenticity Verification and Additional Information

______________________________________________________________________________

1) Problem Description and Brief Discussion

   The X server memory can be accessed my a malicious X client by exploiting
   a missing range check in the function XCreatePixmap(). This bug can probably
   be used to execute arbitrary code with the privileges of the X server (root).

2) Solution or Work-Around

   There is no work-around known.

3) Special Instructions and Notes

   Please restart your X system completely. (Logout of your Windowmanager,
   run "init3;init 5" as root on a console.)

4) Package Location and Checksums

   The preferred method for installing security updates is to use the YaST
   Online Update (YOU) tool. YOU detects which updates are required and
   automatically performs the necessary steps to verify and install them.
   Alternatively, download the update packages for your distribution manually
   and verify their integrity by the methods listed in Section 6 of this
   announcement. Then install the packages using the command

     rpm -Fhv 

   to apply the update, replacing  with the filename of the
   downloaded RPM package.

    x86 Platform:

    SUSE Linux 9.3:
          dc41dbe04424ef869811323b76c567ef
    patch rpm(s):
          cb854e1f0042916a731e2fce9028fcc5
    source rpm(s):
          ca3baf4c2d1df7bfcb0af630bbef1a6d

    SUSE Linux 9.2:
          a08df5563bc23ce0a304a488657f1d53
    patch rpm(s):
          9739cdfa5157b5aa9ba5f0a21129edfd
    source rpm(s):
          de447aaeae832d524d1b292e83a9e6aa

    SUSE Linux 9.1:
          c101e4dfb938ab0b6afb4e480971cb98
    patch rpm(s):
          9117e86e254c3a6ebf73395307382179
    source rpm(s):
          ec3f9bfed9da411ddbc55f8f3bc48729

    SUSE Linux 9.0:
          d85636745eefd2fe67d4ef0d7491bd44
    patch rpm(s):
          a205fbaef7d98c3ce599f71f8dd51864
    source rpm(s):
          3c5c345435ff6310ce8479497a6a80af



    x86-64 Platform:

    SUSE Linux 9.3:
          15895f47f57e2507e8d5ae4e854c3e3a
    patch rpm(s):
          6e58d518d719d901fe4b41ba1a2bd8fa
    source rpm(s):
          ca3baf4c2d1df7bfcb0af630bbef1a6d

    SUSE Linux 9.2:
          f6c86f558fd5ae340f98eb85cbcb5d8d
    patch rpm(s):
          2393163cd16ec2db996f927121f5b6a7
    source rpm(s):
          de447aaeae832d524d1b292e83a9e6aa

    SUSE Linux 9.1:
          9b8f7d8ef0992b6664071f8416243c25
    patch rpm(s):
          918bad600f482fd524da5efc8f7aeb7a
    source rpm(s):
          0cd5570ed44f6dcf2dcfaf28dd1d29f5

    SUSE Linux 9.0:
          fbb16e807e443d1176e346f500abe14f
    patch rpm(s):
          69c56321cba9860b092183f78bdf9d85
    source rpm(s):
          0e6a2a4f3a79421c9ab7042f3500e109

   Our maintenance customers are notified individually. The packages are
   offered for installation from the maintenance web:

      https://www.suse.com:443/

      https://www.suse.com:443/

______________________________________________________________________________

5) Pending Vulnerabilities, Solutions, and Work-Arounds:

   none
______________________________________________________________________________

6) Authenticity Verification and Additional Information

  - Announcement authenticity verification:

    SUSE security announcements are published via mailing lists and on Web
    sites. The authenticity and integrity of a SUSE security announcement is
    guaranteed by a cryptographic signature in each announcement. All SUSE
    security announcements are published with a valid signature.

    To verify the signature of the announcement, save it as text into a file
    and run the command

      gpg --verify 

    replacing  with the name of the file where you saved the
    announcement. The output for a valid signature looks like:

      gpg: Signature made  using RSA key ID 3D25D3D9
      gpg: Good signature from "SuSE Security Team "

    where  is replaced by the date the document was signed.

    If the security team's key is not contained in your key ring, you can
    import it from the first installation CD. To import the key, use the
    command

      gpg --import gpg-pubkey-3d25d3d9-36e12d04.asc

  - Package authenticity verification:

    SUSE update packages are available on many mirror FTP servers all over the
    world. While this service is considered valuable and important to the free
    and open source software community, the authenticity and the integrity of
    a package needs to be verified to ensure that it has not been tampered
    with.

    There are two verification methods that can be used independently from
    each other to prove the authenticity of a downloaded file or RPM package:

    1) Using the internal gpg signatures of the rpm package
    2) MD5 checksums as provided in this announcement

    1) The internal rpm package signatures provide an easy way to verify the
       authenticity of an RPM package. Use the command

        rpm -v --checksig 

       to verify the signature of the package, replacing  with the
       filename of the RPM package downloaded. The package is unmodified if it
       contains a valid signature from build@suse.de with the key ID 9C800ACA.

       This key is automatically imported into the RPM database (on
       RPMv4-based distributions) and the gpg key ring of 'root' during
       installation. You can also find it on the first installation CD and at
       the end of this announcement.

    2) If you need an alternative means of verification, use the md5sum
       command to verify the authenticity of the packages. Execute the command

         md5sum 

       after you downloaded the file from a SUSE FTP server or its mirrors.
       Then compare the resulting md5sum with the one that is listed in the
       SUSE security announcement. Because the announcement containing the
       checksums is cryptographically signed (by security@suse.de), the
       checksums show proof of the authenticity of the package if the
       signature of the announcement is valid. Note that the md5 sums
       published in the SUSE Security Announcements are valid for the
       respective packages only. Newer versions of these packages cannot be
       verified.

  - SUSE runs two security mailing lists to which any interested party may
    subscribe:

    suse-security@suse.com
        -   General Linux and SUSE security discussion.
            All SUSE security announcements are sent to this list.
            To subscribe, send an e-mail to
                .

    suse-security-announce@suse.com
        -   SUSE's announce-only mailing list.
            Only SUSE's security announcements are sent to this list.
            To subscribe, send an e-mail to
                .

    For general information or the frequently asked questions (FAQ),
    send mail to  or
    .

    ====================================================================    SUSE's security contact is  or .
    The  public key is listed below.
    ====================================================================

SuSE: 2005-056: XFree86-server,xorg-x11-server Security Update

September 26, 2005
The X server memory can be accessed my a malicious X client by exploiting The X server memory can be accessed my a malicious X client by exploiting a missing range check in the fun...

Summary


-----BEGIN PGP SIGNED MESSAGE-----

______________________________________________________________________________

                        SUSE Security Announcement

        Package:                XFree86-server,xorg-x11-server
        Announcement ID:        SUSE-SA:2005:056
        Date:                   Mon, 26 Sep 2005 14:00:00 +0000
        Affected Products:      SUSE LINUX 9.0, 9.1, 9.2, 9.3
                                SUSE Linux Desktop 1.0
                                SUSE Linux Enterprise Server 8, 9
                                Novell Linux Desktop 9
        Vulnerability Type:     remote command execution
        Severity (1-10):        9
        SUSE Default Package:   yes
        Cross-References:       CAN-2005-2495

    Content of This Advisory:
        1) Security Vulnerability Resolved:
             pixmap integer overflow
           Problem Description
        2) Solution or Work-Around
        3) Special Instructions and Notes
        4) Package Location and Checksums
        5) Pending Vulnerabilities, Solutions, and Work-Arounds:
            none
        6) Authenticity Verification and Additional Information

______________________________________________________________________________

1) Problem Description and Brief Discussion

   The X server memory can be accessed my a malicious X client by exploiting
   a missing range check in the function XCreatePixmap(). This bug can probably
   be used to execute arbitrary code with the privileges of the X server (root).

2) Solution or Work-Around

   There is no work-around known.

3) Special Instructions and Notes

   Please restart your X system completely. (Logout of your Windowmanager,
   run "init3;init 5" as root on a console.)

4) Package Location and Checksums

   The preferred method for installing security updates is to use the YaST
   Online Update (YOU) tool. YOU detects which updates are required and
   automatically performs the necessary steps to verify and install them.
   Alternatively, download the update packages for your distribution manually
   and verify their integrity by the methods listed in Section 6 of this
   announcement. Then install the packages using the command

     rpm -Fhv 

   to apply the update, replacing  with the filename of the
   downloaded RPM package.

    x86 Platform:

    SUSE Linux 9.3:
          dc41dbe04424ef869811323b76c567ef
    patch rpm(s):
          cb854e1f0042916a731e2fce9028fcc5
    source rpm(s):
          ca3baf4c2d1df7bfcb0af630bbef1a6d

    SUSE Linux 9.2:
          a08df5563bc23ce0a304a488657f1d53
    patch rpm(s):
          9739cdfa5157b5aa9ba5f0a21129edfd
    source rpm(s):
          de447aaeae832d524d1b292e83a9e6aa

    SUSE Linux 9.1:
          c101e4dfb938ab0b6afb4e480971cb98
    patch rpm(s):
          9117e86e254c3a6ebf73395307382179
    source rpm(s):
          ec3f9bfed9da411ddbc55f8f3bc48729

    SUSE Linux 9.0:
          d85636745eefd2fe67d4ef0d7491bd44
    patch rpm(s):
          a205fbaef7d98c3ce599f71f8dd51864
    source rpm(s):
          3c5c345435ff6310ce8479497a6a80af



    x86-64 Platform:

    SUSE Linux 9.3:
          15895f47f57e2507e8d5ae4e854c3e3a
    patch rpm(s):
          6e58d518d719d901fe4b41ba1a2bd8fa
    source rpm(s):
          ca3baf4c2d1df7bfcb0af630bbef1a6d

    SUSE Linux 9.2:
          f6c86f558fd5ae340f98eb85cbcb5d8d
    patch rpm(s):
          2393163cd16ec2db996f927121f5b6a7
    source rpm(s):
          de447aaeae832d524d1b292e83a9e6aa

    SUSE Linux 9.1:
          9b8f7d8ef0992b6664071f8416243c25
    patch rpm(s):
          918bad600f482fd524da5efc8f7aeb7a
    source rpm(s):
          0cd5570ed44f6dcf2dcfaf28dd1d29f5

    SUSE Linux 9.0:
          fbb16e807e443d1176e346f500abe14f
    patch rpm(s):
          69c56321cba9860b092183f78bdf9d85
    source rpm(s):
          0e6a2a4f3a79421c9ab7042f3500e109

   Our maintenance customers are notified individually. The packages are
   offered for installation from the maintenance web:

      https://www.suse.com:443/

      https://www.suse.com:443/

______________________________________________________________________________

5) Pending Vulnerabilities, Solutions, and Work-Arounds:

   none
______________________________________________________________________________

6) Authenticity Verification and Additional Information

  - Announcement authenticity verification:

    SUSE security announcements are published via mailing lists and on Web
    sites. The authenticity and integrity of a SUSE security announcement is
    guaranteed by a cryptographic signature in each announcement. All SUSE
    security announcements are published with a valid signature.

    To verify the signature of the announcement, save it as text into a file
    and run the command

      gpg --verify 

    replacing  with the name of the file where you saved the
    announcement. The output for a valid signature looks like:

      gpg: Signature made  using RSA key ID 3D25D3D9
      gpg: Good signature from "SuSE Security Team "

    where  is replaced by the date the document was signed.

    If the security team's key is not contained in your key ring, you can
    import it from the first installation CD. To import the key, use the
    command

      gpg --import gpg-pubkey-3d25d3d9-36e12d04.asc

  - Package authenticity verification:

    SUSE update packages are available on many mirror FTP servers all over the
    world. While this service is considered valuable and important to the free
    and open source software community, the authenticity and the integrity of
    a package needs to be verified to ensure that it has not been tampered
    with.

    There are two verification methods that can be used independently from
    each other to prove the authenticity of a downloaded file or RPM package:

    1) Using the internal gpg signatures of the rpm package
    2) MD5 checksums as provided in this announcement

    1) The internal rpm package signatures provide an easy way to verify the
       authenticity of an RPM package. Use the command

        rpm -v --checksig 

       to verify the signature of the package, replacing  with the
       filename of the RPM package downloaded. The package is unmodified if it
       contains a valid signature from build@suse.de with the key ID 9C800ACA.

       This key is automatically imported into the RPM database (on
       RPMv4-based distributions) and the gpg key ring of 'root' during
       installation. You can also find it on the first installation CD and at
       the end of this announcement.

    2) If you need an alternative means of verification, use the md5sum
       command to verify the authenticity of the packages. Execute the command

         md5sum 

       after you downloaded the file from a SUSE FTP server or its mirrors.
       Then compare the resulting md5sum with the one that is listed in the
       SUSE security announcement. Because the announcement containing the
       checksums is cryptographically signed (by security@suse.de), the
       checksums show proof of the authenticity of the package if the
       signature of the announcement is valid. Note that the md5 sums
       published in the SUSE Security Announcements are valid for the
       respective packages only. Newer versions of these packages cannot be
       verified.

  - SUSE runs two security mailing lists to which any interested party may
    subscribe:

    suse-security@suse.com
        -   General Linux and SUSE security discussion.
            All SUSE security announcements are sent to this list.
            To subscribe, send an e-mail to
                .

    suse-security-announce@suse.com
        -   SUSE's announce-only mailing list.
            Only SUSE's security announcements are sent to this list.
            To subscribe, send an e-mail to
                .

    For general information or the frequently asked questions (FAQ),
    send mail to  or
    .

    ====================================================================    SUSE's security contact is  or .
    The  public key is listed below.
    ====================================================================

References

Severity

Related News