The following two security updates are available:

- Security Announcement: acroread (SUSE-SA:2010:037)
- SUSE Security Announcement: kernel (SUSE-SA:2010:036)



[security-announce] Security Announcement: acroread (SUSE-SA:2010:037)

______________________________________________________________________________

SUSE Security Announcement

Package: acroread
Announcement ID: SUSE-SA:2010:037
Date: Wed, 01 Sep 2010 11:00:00 +0000
Affected Products: openSUSE 11.1
openSUSE 11.2
openSUSE 11.3
SUSE Linux Enterprise Desktop 10 SP3
SUSE Linux Enterprise Desktop 11
SUSE Linux Enterprise Desktop 11 SP1
Vulnerability Type: remote code execution
CVSS v2 Base Score: 9.3 (AV:N/AC:M/Au:N/C:C/I:C/A:C)
SUSE Default Package: no
Cross-References: CVE-2010-0209, CVE-2010-1240, CVE-2010-2188
CVE-2010-2213, CVE-2010-2214, CVE-2010-2215
CVE-2010-2216, CVE-2010-2862

Content of This Advisory:
1) Security Vulnerability Resolved:
Acrobat Reader security update
Problem Description
2) Solution or Work-Around
3) Special Instructions and Notes
4) Package Location and Checksums
5) Pending Vulnerabilities, Solutions, and Work-Arounds:
- See SUSE Security Summary Report
6) Authenticity Verification and Additional Information

______________________________________________________________________________

1) Problem Description and Brief Discussion

Specially crafted PDF documents could crash acroread or lead to
execution of arbitrary code (CVE-2010-1240, CVE-2010-2862).

This update also incorporate the Adobe Flash Player update APSB10-16
for the bundled flash player parts (CVE-2010-0209, CVE-2010-2188,
CVE-2010-2213, CVE-2010-2214, CVE-2010-2215, CVE-2010-2216).

Please see Adobe's site for more information:
http://www.adobe.com/support/security/bulletins/apsb10-17.html
2) Solution or Work-Around

There is no known workaround, please install the update packages.

3) Special Instructions and Notes

Please close and restart all running instances of acroread after the update.

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:

openSUSE 11.3:
http://download.opensuse.org/update/11.3/rpm/i586/acroread-9.3.4-0.2.1.i586.rpm

openSUSE 11.2:
http://download.opensuse.org/update/11.2/rpm/i586/acroread-9.3.4-0.3.1.i586.rpm

openSUSE 11.1:
http://download.opensuse.org/update/11.1/rpm/i586/acroread-9.3.4-0.3.1.i586.rpm

Platform Independent:

openSUSE 11.2:
http://download.opensuse.org/update/11.2/rpm/noarch/acroread-cmaps-9.3.4-0.3.1.noarch.rpm
http://download.opensuse.org/update/11.2/rpm/noarch/acroread-fonts-ja-9.3.4-0.3.1.noarch.rpm
http://download.opensuse.org/update/11.2/rpm/noarch/acroread-fonts-ko-9.3.4-0.3.1.noarch.rpm
http://download.opensuse.org/update/11.2/rpm/noarch/acroread-fonts-zh_CN-9.3.4-0.3.1.noarch.rpm
http://download.opensuse.org/update/11.2/rpm/noarch/acroread-fonts-zh_TW-9.3.4-0.3.1.noarch.rpm

openSUSE 11.1:
http://download.opensuse.org/update/11.1/rpm/noarch/acroread-cmaps-9.3.4-0.3.1.noarch.rpm
http://download.opensuse.org/update/11.1/rpm/noarch/acroread-fonts-ja-9.3.4-0.3.1.noarch.rpm
http://download.opensuse.org/update/11.1/rpm/noarch/acroread-fonts-ko-9.3.4-0.3.1.noarch.rpm
http://download.opensuse.org/update/11.1/rpm/noarch/acroread-fonts-zh_CN-9.3.4-0.3.1.noarch.rpm
http://download.opensuse.org/update/11.1/rpm/noarch/acroread-fonts-zh_TW-9.3.4-0.3.1.noarch.rpm

Sources:

openSUSE 11.3:
http://download.opensuse.org/update/11.3/rpm/src/acroread-9.3.4-0.2.1.nosrc.rpm

openSUSE 11.2:
http://download.opensuse.org/update/11.2/rpm/src/acroread-9.3.4-0.3.1.nosrc.rpm
http://download.opensuse.org/update/11.2/rpm/src/acroread-cmaps-9.3.4-0.3.1.nosrc.rpm

openSUSE 11.1:
http://download.opensuse.org/update/11.1/rpm/src/acroread-9.3.4-0.3.1.nosrc.rpm
http://download.opensuse.org/update/11.1/rpm/src/acroread-cmaps-9.3.4-0.3.1.nosrc.rpm

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

SUSE Linux Enterprise Desktop 10 SP3
http://download.novell.com/patch/finder/?keywords=8d6734b9845d252567cc853032034436
http://download.novell.com/patch/finder/?keywords=0dc88ee261caadcb967f90fbfd30e7f2

SUSE Linux Enterprise Desktop 11 SP1
http://download.novell.com/patch/finder/?keywords=36a9cbb312d6ad766eed81d158f1dc01
http://download.novell.com/patch/finder/?keywords=f1ea8f5a6e6b82355c9b5987cea86fa1

SUSE Linux Enterprise Desktop 11
http://download.novell.com/patch/finder/?keywords=095cf91c7a73fc7f8adfcb7b68dd1ea9
http://download.novell.com/patch/finder/?keywords=df4199604d1ebfce8b612958957eb533

______________________________________________________________________________

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

- See SUSE Security Summary Report


______________________________________________________________________________

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.

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.

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

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

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

[security-announce] SUSE Security Announcement: kernel (SUSE-SA:2010:036)

_____________________________________________________________________________

SUSE Security Announcement

Package: kernel
Announcement ID: SUSE-SA:2010:036
Date: Wed, 01 Sep 2010 11:00:00 +0000
Affected Products: SUSE SLES 9
Open Enterprise Server
Novell Linux POS 9
Vulnerability Type: remote denial of service
CVSS v2 Base Score: 7.8 (AV:N/AC:L/Au:N/C:N/I:N/A:C)
SUSE Default Package: yes
Cross-References: CVE-2007-6206, CVE-2007-6733, CVE-2008-0598
CVE-2008-3275, CVE-2009-1389, CVE-2009-4020
CVE-2009-4537, CVE-2010-0727, CVE-2010-1083
CVE-2010-1088, CVE-2010-1188, CVE-2010-2521

Content of This Advisory:
1) Security Vulnerability Resolved:
Linux kernel security update
Problem Description
2) Solution or Work-Around
3) Special Instructions and Notes
4) Package Location and Checksums
5) Pending Vulnerabilities, Solutions, and Work-Arounds:
- See SUSE Security Summary Report
6) Authenticity Verification and Additional Information

______________________________________________________________________________

1) Problem Description and Brief Discussion

This update fixes various security issues and some bugs in the SUSE Linux
Enterprise 9 kernel.

Following security issues were fixed:
CVE-2010-2521: A crafted NFS write request might have caused a buffer overwrite,
potentially causing a kernel crash.

CVE-2008-0598: The x86_64 copy_to_user implementation might have leaked kernel
memory depending on specific user buffer setups.

CVE-2009-4537: drivers/net/r8169.c in the r8169 driver in the Linux kernel
did not properly check the size of an Ethernet frame that exceeds the MTU,
which allows remote attackers to (1) cause a denial of service (temporary
network outage) via a packet with a crafted size, in conjunction with
certain packets containing A characters and certain packets containing E
characters; or (2) cause a denial of service (system crash) via a packet
with a crafted size, in conjunction with certain packets containing '\0'
characters, related to the value of the status register and erroneous
behavior associated with the RxMaxSize register. NOTE: this vulnerability
exists because of an incorrect fix for CVE-2009-1389.

CVE-2010-1188: Use-after-free vulnerability in net/ipv4/tcp_input.c in
the Linux kernel 2.6 when IPV6_RECVPKTINFO is set on a listening socket,
allowed remote attackers to cause a denial of service (kernel panic)
via a SYN packet while the socket is in a listening (TCP_LISTEN) state,
which is not properly handled causes the skb structure to be freed.

CVE-2008-3275: The (1) real_lookup and (2) __lookup_hash functions
in fs/namei.c in the vfs implementation in the Linux kernel did not
prevent creation of a child dentry for a deleted (aka S_DEAD) directory,
which allowed local users to cause a denial of service ("overflow" of
the UBIFS orphan area) via a series of attempted file creations within
deleted directories.

CVE-2007-6733: The nfs_lock function in fs/nfs/file.c in the Linux kernel
did not properly remove POSIX locks on files that are setgid without
group-execute permission, which allows local users to cause a denial of
service (BUG and system crash) by locking a file on an NFS filesystem and
then changing this files permissions, a related issue to CVE-2010-0727.

CVE-2007-6206: The do_coredump function in fs/exec.c in Linux kernel
did not change the UID of a core dump file if it exists before a root
process creates a core dump in the same location, which might have allowed
local users to obtain sensitive information.

CVE-2010-1088: fs/namei.c in the Linux kernel did not always follow NFS
automount "symlinks," which allowed attackers to have an unknown impact,
related to LOOKUP_FOLLOW.

CVE-2009-4020: Stack-based buffer overflow in the hfs subsystem in the
Linux kernel allowed remote attackers to have an unspecified impact
via a crafted Hierarchical File System (HFS) filesystem, related to the
hfs_readdir function in fs/hfs/dir.c.

CVE-2010-1083: The processcompl_compat function in
drivers/usb/core/devio.c in Linux kernel did not clear the transfer
buffer before returning to userspace when a USB command fails, which
might have made it easier for physically proximate attackers to obtain
sensitive information (kernel memory).

2) Solution or Work-Around

There is no known workaround, please install the update packages.

3) Special Instructions and Notes

Please reboot the machine after installing the update.

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.

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

SUSE CORE 9 for AMD64 and Intel EM64T
http://download.novell.com/patch/finder/?keywords=b13b7c37b794913aaef1d239c08b31ab

SUSE CORE 9 for IBM zSeries 64bit
http://download.novell.com/patch/finder/?keywords=5d5bd50baa9a4fcb6b4fda8d7a3a79f3

SUSE CORE 9 for IBM S/390 31bit
http://download.novell.com/patch/finder/?keywords=ec0907a749db912429f923a2bbfdcfff

SUSE CORE 9 for IBM POWER
http://download.novell.com/patch/finder/?keywords=dd0f13d71502c69174ee0008c6ae7a63

SUSE CORE 9 for Itanium Processor Family
http://download.novell.com/patch/finder/?keywords=a3f3f41a042648ecf313d65b8ff974ac

Novell Linux POS 9
http://download.novell.com/patch/finder/?keywords=46a94f2d03cb2089d641b6390867fd8a

SUSE SLES 9
http://download.novell.com/patch/finder/?keywords=b13b7c37b794913aaef1d239c08b31ab
http://download.novell.com/patch/finder/?keywords=5d5bd50baa9a4fcb6b4fda8d7a3a79f3
http://download.novell.com/patch/finder/?keywords=ec0907a749db912429f923a2bbfdcfff
http://download.novell.com/patch/finder/?keywords=dd0f13d71502c69174ee0008c6ae7a63
http://download.novell.com/patch/finder/?keywords=a3f3f41a042648ecf313d65b8ff974ac
http://download.novell.com/patch/finder/?keywords=46a94f2d03cb2089d641b6390867fd8a

SUSE CORE 9 for x86
http://download.novell.com/patch/finder/?keywords=46a94f2d03cb2089d641b6390867fd8a

Open Enterprise Server
http://download.novell.com/patch/finder/?keywords=c14f8a2a7882052067244604d07964d9
http://download.novell.com/patch/finder/?keywords=e0b5a1783f742694f60bf1c4d1f86599

______________________________________________________________________________

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

- See SUSE Security Summary Report

______________________________________________________________________________

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.

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.

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

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

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