Advisories, December 6, 2005

Fedora Core

Fedora Update Notification
FEDORA-2005-1121
2005-12-06

Product : Fedora Core 3
Name : xpdf
Version : 3.01
Release : 0.FC3.3
Summary : A PDF file viewer for the X Window System.

Description :
Xpdf is an X Window System based viewer for Portable Document
Format (PDF) files. Xpdf is a small and efficient program which
uses standard X fonts.

Update Information:

Several flaws were discovered in Xpdf. An attacker could
construct a carefully crafted PDF file that could cause Xpdf to
crash or possibly execute arbitrary code when opened. The Common
Vulnerabilities and Exposures project assigned the name
CAN-2005-3193 to these issues.

Users of Xpdf should upgrade to this updated package, which
contains a patch to resolve these issues.

Tue Dec 6 2005 Than Ngo <than@redhat.com> 1:3.01-0.FC3.3
- apply upstream patch to fix CAN-2005-3193

This update can be downloaded from:

http://download.fedora.redhat.com/pub/fedora/linux/core/updates/3/

69dc1262d4ac1a7f706554a2aa278f1b
SRPMS/xpdf-3.01-0.FC3.3.src.rpm
1c49642003d2017d0789eed36c409b8b
x86_64/xpdf-3.01-0.FC3.3.x86_64.rpm
74af76cadc5d90674a21d1b0e1c245b9
x86_64/debug/xpdf-debuginfo-3.01-0.FC3.3.x86_64.rpm
e87089ed6646877e1ed54018d42dd852
i386/xpdf-3.01-0.FC3.3.i386.rpm
4ec6a4425385b8de2ff961aa738cfd65
i386/debug/xpdf-debuginfo-3.01-0.FC3.3.i386.rpm

This update can also be installed with the Update Agent; you can
launch the Update Agent with the ‘up2date’ command.

Fedora Update Notification
FEDORA-2005-1122
2005-12-06

Product : Fedora Core 4
Name : xpdf
Version : 3.01
Release : 0.FC4.3
Summary : A PDF file viewer for the X Window System.

Description :
Xpdf is an X Window System based viewer for Portable Document
Format (PDF) files. Xpdf is a small and efficient program which
uses standard X fonts.

Update Information:

Users of Xpdf should upgrade to this updated package, which
contains a patch to resolve these issues.

Mon Nov 7 2005 Than Ngo <than@redhat.com> 1:3.01-0.FC4.3
- apply upstream patch to fix security holes in Xpdf

This update can be downloaded from:

http://download.fedora.redhat.com/pub/fedora/linux/core/updates/4/

e439b80c57a6ca7d5e2b38f8ae7d276c
SRPMS/xpdf-3.01-0.FC4.3.src.rpm
0ee28635d60f65d2d8acc9ae0fe5d7b2 ppc/xpdf-3.01-0.FC4.3.ppc.rpm
729d05aa72aa61af710115ea94fc6954
ppc/debug/xpdf-debuginfo-3.01-0.FC4.3.ppc.rpm
2a191c74800dd66255ac18857c12ac5d
x86_64/xpdf-3.01-0.FC4.3.x86_64.rpm
ee1cd4cccec3a0b3bb72de3a72f4ce9a
x86_64/debug/xpdf-debuginfo-3.01-0.FC4.3.x86_64.rpm
c7c92841cec26466b576208d14feed9e
i386/xpdf-3.01-0.FC4.3.i386.rpm
9ec2d56a438aaa69029a440803f7b802
i386/debug/xpdf-debuginfo-3.01-0.FC4.3.i386.rpm

This update can also be installed with the Update Agent; you can
launch the Update Agent with the ‘up2date’ command.

Red Hat Linux

Red Hat Security Advisory

Synopsis: Important: xpdf security update
Advisory ID: RHSA-2005:840-01
Advisory URL: https://rhn.redhat.com/errata/RHSA-2005-840.html

Issue date: 2005-12-06
Updated on: 2005-12-06
Product: Red Hat Enterprise Linux
CVE Names: CAN-2005-3193

1. Summary:

An updated xpdf package that fixes several security issues is
now available.

This update has been rated as having important security impact
by the Red Hat Security Response Team.

2. Relevant releases/architectures:

Red Hat Enterprise Linux AS (Advanced Server) version 2.1 –
i386, ia64
Red Hat Linux Advanced Workstation 2.1 – ia64
Red Hat Enterprise Linux ES version 2.1 – i386
Red Hat Enterprise Linux WS version 2.1 – i386
Red Hat Enterprise Linux AS version 3 – i386, ia64, ppc, s390,
s390x, x86_64
Red Hat Desktop version 3 – i386, x86_64
Red Hat Enterprise Linux ES version 3 – i386, ia64, x86_64
Red Hat Enterprise Linux WS version 3 – i386, ia64, x86_64
Red Hat Enterprise Linux AS version 4 – i386, ia64, ppc, s390,
s390x, x86_64
Red Hat Enterprise Linux Desktop version 4 – i386, x86_64
Red Hat Enterprise Linux ES version 4 – i386, ia64, x86_64
Red Hat Enterprise Linux WS version 4 – i386, ia64, x86_64

3. Problem description:

The xpdf package is an X Window System-based viewer for Portable
Document Format (PDF) files.

Users of Xpdf should upgrade to this updated package, which
contains a backported patch to resolve these issues.

Red Hat would like to thank Derek B. Noonburg for reporting this
issue and providing a patch.

4. Solution:

Before applying this update, make sure that all
previously-released errata relevant to your system have been
applied. Use Red Hat Network to download and update your packages.
To launch the Red Hat Update Agent, use the following command:

up2date

For information on how to install packages manually, refer to
the following Web page for the System Administration or
Customization guide specific to your system:

http://www.redhat.com/docs/manuals/enterprise/

5. Bug IDs fixed (http://bugzilla.redhat.com/):

173888 – CVE-2005-3193 xpdf issues

6. RPMs required:

Red Hat Enterprise Linux AS (Advanced Server) version 2.1:

SRPMS:

ftp://updates.redhat.com/enterprise/2.1AS/en/os/SRPMS/xpdf-0.92-16.src.rpm

7a1ec5ee2b0e182671178e129d23d02f xpdf-0.92-16.src.rpm

i386:
631fd9d85e54b843f39cfece3c96e299 xpdf-0.92-16.i386.rpm

ia64:
bd83cdfddc43521d6877fef706fda973 xpdf-0.92-16.ia64.rpm

Red Hat Linux Advanced Workstation 2.1:

SRPMS:

ftp://updates.redhat.com/enterprise/2.1AW/en/os/SRPMS/xpdf-0.92-16.src.rpm

7a1ec5ee2b0e182671178e129d23d02f xpdf-0.92-16.src.rpm

ia64:
bd83cdfddc43521d6877fef706fda973 xpdf-0.92-16.ia64.rpm

Red Hat Enterprise Linux ES version 2.1:

SRPMS:

ftp://updates.redhat.com/enterprise/2.1ES/en/os/SRPMS/xpdf-0.92-16.src.rpm

7a1ec5ee2b0e182671178e129d23d02f xpdf-0.92-16.src.rpm

i386:
631fd9d85e54b843f39cfece3c96e299 xpdf-0.92-16.i386.rpm

Red Hat Enterprise Linux WS version 2.1:

SRPMS:

ftp://updates.redhat.com/enterprise/2.1WS/en/os/SRPMS/xpdf-0.92-16.src.rpm

7a1ec5ee2b0e182671178e129d23d02f xpdf-0.92-16.src.rpm

i386:
631fd9d85e54b843f39cfece3c96e299 xpdf-0.92-16.i386.rpm

Red Hat Enterprise Linux AS version 3:

SRPMS:

ftp://updates.redhat.com/enterprise/3AS/en/os/SRPMS/xpdf-2.02-9.7.src.rpm

2faf50967ceb94d897d52eb9c29429c3 xpdf-2.02-9.7.src.rpm

i386:
e5ec318a045404236d7515c512c52e18 xpdf-2.02-9.7.i386.rpm

ia64:
1dc462b0bfeb0a11a608d2de041adafd xpdf-2.02-9.7.ia64.rpm

ppc:
0d98945bc02703d08dbf833d0e1787aa xpdf-2.02-9.7.ppc.rpm

s390:
3cb519b83be112558603623fee44c528 xpdf-2.02-9.7.s390.rpm

s390x:
eac98a768aa2c0b25af4d102ff1569b8 xpdf-2.02-9.7.s390x.rpm

x86_64:
a6e7d4a9449af1f6147b094497aa33b9 xpdf-2.02-9.7.x86_64.rpm

Red Hat Desktop version 3:

SRPMS:

ftp://updates.redhat.com/enterprise/3desktop/en/os/SRPMS/xpdf-2.02-9.7.src.rpm

2faf50967ceb94d897d52eb9c29429c3 xpdf-2.02-9.7.src.rpm

i386:
e5ec318a045404236d7515c512c52e18 xpdf-2.02-9.7.i386.rpm

x86_64:
a6e7d4a9449af1f6147b094497aa33b9 xpdf-2.02-9.7.x86_64.rpm

Red Hat Enterprise Linux ES version 3:

SRPMS:

ftp://updates.redhat.com/enterprise/3ES/en/os/SRPMS/xpdf-2.02-9.7.src.rpm

2faf50967ceb94d897d52eb9c29429c3 xpdf-2.02-9.7.src.rpm

i386:
e5ec318a045404236d7515c512c52e18 xpdf-2.02-9.7.i386.rpm

ia64:
1dc462b0bfeb0a11a608d2de041adafd xpdf-2.02-9.7.ia64.rpm

x86_64:
a6e7d4a9449af1f6147b094497aa33b9 xpdf-2.02-9.7.x86_64.rpm

Red Hat Enterprise Linux WS version 3:

SRPMS:

ftp://updates.redhat.com/enterprise/3WS/en/os/SRPMS/xpdf-2.02-9.7.src.rpm

2faf50967ceb94d897d52eb9c29429c3 xpdf-2.02-9.7.src.rpm

i386:
e5ec318a045404236d7515c512c52e18 xpdf-2.02-9.7.i386.rpm

ia64:
1dc462b0bfeb0a11a608d2de041adafd xpdf-2.02-9.7.ia64.rpm

x86_64:
a6e7d4a9449af1f6147b094497aa33b9 xpdf-2.02-9.7.x86_64.rpm

Red Hat Enterprise Linux AS version 4:

SRPMS:

ftp://updates.redhat.com/enterprise/4AS/en/os/SRPMS/xpdf-3.00-11.9.src.rpm

4a2f45dcb7f3fae59d0e8f1c50c646e8 xpdf-3.00-11.9.src.rpm

i386:
f163be62a078caab1af3dcda85b9245a xpdf-3.00-11.9.i386.rpm

ia64:
7efbfbbabf316a14db820ab56dba5c33 xpdf-3.00-11.9.ia64.rpm

ppc:
d8352411a6ea0994d8dbd1aa607395bf xpdf-3.00-11.9.ppc.rpm

s390:
29e164b50b4e59d2211658d965a9168b xpdf-3.00-11.9.s390.rpm

s390x:
ff27714a2c97cf072a87517b38c117c9 xpdf-3.00-11.9.s390x.rpm

x86_64:
e39e5160c5f8da5bbd850f411bc09cee xpdf-3.00-11.9.x86_64.rpm

Red Hat Enterprise Linux Desktop version 4:

SRPMS:

ftp://updates.redhat.com/enterprise/4Desktop/en/os/SRPMS/xpdf-3.00-11.9.src.rpm

4a2f45dcb7f3fae59d0e8f1c50c646e8 xpdf-3.00-11.9.src.rpm

i386:
f163be62a078caab1af3dcda85b9245a xpdf-3.00-11.9.i386.rpm

x86_64:
e39e5160c5f8da5bbd850f411bc09cee xpdf-3.00-11.9.x86_64.rpm

Red Hat Enterprise Linux ES version 4:

SRPMS:

ftp://updates.redhat.com/enterprise/4ES/en/os/SRPMS/xpdf-3.00-11.9.src.rpm

4a2f45dcb7f3fae59d0e8f1c50c646e8 xpdf-3.00-11.9.src.rpm

i386:
f163be62a078caab1af3dcda85b9245a xpdf-3.00-11.9.i386.rpm

ia64:
7efbfbbabf316a14db820ab56dba5c33 xpdf-3.00-11.9.ia64.rpm

x86_64:
e39e5160c5f8da5bbd850f411bc09cee xpdf-3.00-11.9.x86_64.rpm

Red Hat Enterprise Linux WS version 4:

SRPMS:

ftp://updates.redhat.com/enterprise/4WS/en/os/SRPMS/xpdf-3.00-11.9.src.rpm

4a2f45dcb7f3fae59d0e8f1c50c646e8 xpdf-3.00-11.9.src.rpm

i386:
f163be62a078caab1af3dcda85b9245a xpdf-3.00-11.9.i386.rpm

ia64:
7efbfbbabf316a14db820ab56dba5c33 xpdf-3.00-11.9.ia64.rpm

x86_64:
e39e5160c5f8da5bbd850f411bc09cee xpdf-3.00-11.9.x86_64.rpm

These packages are GPG signed by Red Hat for security. Our key
and details on how to verify the signature are available from
https://www.redhat.com/security/team/key/#package

7. References:

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2005-3193

8. Contact:

The Red Hat security contact is <secalert@redhat.com>. More
contact details at https://www.redhat.com/security/team/contact/

Red Hat Security Advisory

Synopsis: Moderate: libc-client security update
Advisory ID: RHSA-2005:848-01
Advisory URL: https://rhn.redhat.com/errata/RHSA-2005-848.html

Issue date: 2005-12-06
Updated on: 2005-12-06
Product: Red Hat Enterprise Linux
CVE Names: CVE-2005-2933

1. Summary:

Updated libc-client packages that fix a buffer overflow issue
are now available.

This update has been rated as having moderate security impact by
the Red Hat Security Response Team.

2. Relevant releases/architectures:

Red Hat Enterprise Linux AS version 4 – i386, ia64, ppc, s390,
s390x, x86_64
Red Hat Enterprise Linux Desktop version 4 – i386, x86_64
Red Hat Enterprise Linux ES version 4 – i386, ia64, x86_64
Red Hat Enterprise Linux WS version 4 – i386, ia64, x86_64

3. Problem description:

C-client is a common API for accessing mailboxes.

A buffer overflow flaw was discovered in the way C-client parses
user supplied mailboxes. If an authenticated user requests a
specially crafted mailbox name, it may be possible to execute
arbitrary code on a server that uses C-client to access mailboxes.
The Common Vulnerabilities and Exposures project has assigned the
name CVE-2005-2933 to this issue.

All users of libc-client should upgrade to these updated
packages, which contain a backported patch that resolves this
issue.

4. Solution:

Before applying this update, make sure all previously released
errata relevant to your system have been applied.

This update is available via Red Hat Network. To use Red Hat
Network, launch the Red Hat Update Agent with the following
command:

up2date

This will start an interactive process that will result in the
appropriate RPMs being upgraded on your system.

5. Bug IDs fixed (http://bugzilla.redhat.com/):

171344 – CVE-2005-2933 imap buffer overflow

6. RPMs required:

Red Hat Enterprise Linux AS version 4:

SRPMS:

ftp://updates.redhat.com/enterprise/4AS/en/os/SRPMS/libc-client-2002e-14.src.rpm

e050f3b294c3a810f9c62a5a4ad8ee35 libc-client-2002e-14.src.rpm

i386:
c6460f746fa52858d1e617e5aa5f8791 libc-client-2002e-14.i386.rpm
15a992bb5fd6a334e430626d194efb83
libc-client-devel-2002e-14.i386.rpm

ia64:
c6460f746fa52858d1e617e5aa5f8791 libc-client-2002e-14.i386.rpm
d82f92b0aa198d5c57a74f849b6233db libc-client-2002e-14.ia64.rpm
e997fd97ca8970294bb50378ff86de69
libc-client-devel-2002e-14.ia64.rpm

ppc:
895819bc9ab63446494b0771da35da91 libc-client-2002e-14.ppc.rpm
075bae7362a94821ef9b329eca9ab239 libc-client-2002e-14.ppc64.rpm
7a7af03991228dd6e8904f7e6ae152bf
libc-client-devel-2002e-14.ppc.rpm

s390:
782730a8a1ad886fd69ad0918369e5d7 libc-client-2002e-14.s390.rpm
bd98ece7dc7ad68aa1e2d5d54f2c7a30
libc-client-devel-2002e-14.s390.rpm

s390x:
782730a8a1ad886fd69ad0918369e5d7 libc-client-2002e-14.s390.rpm
bede6046b6b14dc2e7e3fe7a7a3c35df libc-client-2002e-14.s390x.rpm
4662ba7a95544c1860fce45152ceb659
libc-client-devel-2002e-14.s390x.rpm

x86_64:
c6460f746fa52858d1e617e5aa5f8791 libc-client-2002e-14.i386.rpm
37898475b279206da3375d5f4d95b91e
libc-client-2002e-14.x86_64.rpm
678b838f2f0e13af8343ccac76c0b82a
libc-client-devel-2002e-14.x86_64.rpm

Red Hat Enterprise Linux Desktop version 4:

SRPMS:

ftp://updates.redhat.com/enterprise/4Desktop/en/os/SRPMS/libc-client-2002e-14.src.rpm

e050f3b294c3a810f9c62a5a4ad8ee35 libc-client-2002e-14.src.rpm

i386:
c6460f746fa52858d1e617e5aa5f8791 libc-client-2002e-14.i386.rpm
15a992bb5fd6a334e430626d194efb83
libc-client-devel-2002e-14.i386.rpm

Red Hat Enterprise Linux ES version 4:

SRPMS:

ftp://updates.redhat.com/enterprise/4ES/en/os/SRPMS/libc-client-2002e-14.src.rpm

e050f3b294c3a810f9c62a5a4ad8ee35 libc-client-2002e-14.src.rpm

i386:
c6460f746fa52858d1e617e5aa5f8791 libc-client-2002e-14.i386.rpm
15a992bb5fd6a334e430626d194efb83
libc-client-devel-2002e-14.i386.rpm

Red Hat Enterprise Linux WS version 4:

SRPMS:

ftp://updates.redhat.com/enterprise/4WS/en/os/SRPMS/libc-client-2002e-14.src.rpm

e050f3b294c3a810f9c62a5a4ad8ee35 libc-client-2002e-14.src.rpm

i386:
c6460f746fa52858d1e617e5aa5f8791 libc-client-2002e-14.i386.rpm
15a992bb5fd6a334e430626d194efb83
libc-client-devel-2002e-14.i386.rpm

These packages are GPG signed by Red Hat for security. Our key
and details on how to verify the signature are available from
https://www.redhat.com/security/team/key/#package

7. References:

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2005-2933

8. Contact:

The Red Hat security contact is <secalert@redhat.com>. More
contact details at https://www.redhat.com/security/team/contact/

Red Hat Security Advisory

Synopsis: Moderate: imap security update
Advisory ID: RHSA-2005:850-01
Advisory URL: https://rhn.redhat.com/errata/RHSA-2005-850.html

Issue date: 2005-12-06
Updated on: 2005-12-06
Product: Red Hat Enterprise Linux
CVE Names: CVE-2005-2933

1. Summary:

An updated imap package that fixes a buffer overflow issue is
now available.

This update has been rated as having moderate security impact by
the Red Hat Security Response Team.

2. Relevant releases/architectures:

Red Hat Enterprise Linux AS (Advanced Server) version 2.1 –
i386, ia64
Red Hat Linux Advanced Workstation 2.1 – ia64
Red Hat Enterprise Linux ES version 2.1 – i386
Red Hat Enterprise Linux AS version 3 – i386, ia64, ppc, s390,
s390x, x86_64
Red Hat Desktop version 3 – i386, x86_64
Red Hat Enterprise Linux ES version 3 – i386, ia64, x86_64
Red Hat Enterprise Linux WS version 3 – i386, ia64, x86_64

3. Problem description:

The imap package provides server daemons for both the IMAP
(Internet Message Access Protocol) and POP (Post Office Protocol)
mail access protocols.

A buffer overflow flaw was discovered in the way the c-client
library parses user supplied mailboxes. If an authenticated user
requests a specially crafted mailbox name, it may be possible to
execute arbitrary code on a server that uses the library. The
Common Vulnerabilities and Exposures project has assigned the name
CVE-2005-2933 to this issue.

All users of imap should upgrade to these updated packages,
which contain a backported patch and are not vulnerable to this
issue.

4. Solution:

Before applying this update, make sure all previously released
errata relevant to your system have been applied.

This update is available via Red Hat Network. To use Red Hat
Network, launch the Red Hat Update Agent with the following
command:

up2date

This will start an interactive process that will result in the
appropriate RPMs being upgraded on your system.

5. Bug IDs fixed (http://bugzilla.redhat.com/):

169953 – CVE-2005-2933 imap buffer overflow

6. RPMs required:

Red Hat Enterprise Linux AS (Advanced Server) version 2.1:

SRPMS:

ftp://updates.redhat.com/enterprise/2.1AS/en/os/SRPMS/imap-2001a-19.src.rpm

368ed3b9cf30c88c562daf57b6dc314f imap-2001a-19.src.rpm

i386:
b04aa8f1b0aa703871346700d28fc64e imap-2001a-19.i386.rpm
1fdbd1eb8cf467af263ed9972df9409d imap-devel-2001a-19.i386.rpm

ia64:
fb5d1b22b2df69c1f468f16df9ebfdce imap-2001a-19.ia64.rpm
5599797731d68a60df45c689a8ceb509 imap-devel-2001a-19.ia64.rpm

Red Hat Linux Advanced Workstation 2.1:

SRPMS:

ftp://updates.redhat.com/enterprise/2.1AW/en/os/SRPMS/imap-2001a-19.src.rpm

368ed3b9cf30c88c562daf57b6dc314f imap-2001a-19.src.rpm

ia64:
fb5d1b22b2df69c1f468f16df9ebfdce imap-2001a-19.ia64.rpm
5599797731d68a60df45c689a8ceb509 imap-devel-2001a-19.ia64.rpm

Red Hat Enterprise Linux ES version 2.1:

SRPMS:

ftp://updates.redhat.com/enterprise/2.1ES/en/os/SRPMS/imap-2001a-19.src.rpm

368ed3b9cf30c88c562daf57b6dc314f imap-2001a-19.src.rpm

i386:
b04aa8f1b0aa703871346700d28fc64e imap-2001a-19.i386.rpm
1fdbd1eb8cf467af263ed9972df9409d imap-devel-2001a-19.i386.rpm

Red Hat Enterprise Linux AS version 3:

SRPMS:

ftp://updates.redhat.com/enterprise/3AS/en/os/SRPMS/imap-2002d-12.src.rpm

8685e5bf17d4768f5254d8bd69debdf1 imap-2002d-12.src.rpm

i386:
7eef6e0ecc4147cc73a60be3e0d76647 imap-2002d-12.i386.rpm
820c2d446fd800cec6ce64ec2c42f494 imap-devel-2002d-12.i386.rpm
88d23ffc188f1d196d60ae43f7aa1939 imap-utils-2002d-12.i386.rpm

ia64:
070f9e193a84fe7d67dd022eb98e4889 imap-2002d-12.ia64.rpm
6b5594df0491c151995d36ec5e88fd63 imap-devel-2002d-12.ia64.rpm
39b5b378efec1b4242c5b5a1ae188846 imap-utils-2002d-12.ia64.rpm

ppc:
f23db230f9b7ecde5cad18cf1a6dd000 imap-2002d-12.ppc.rpm
ac380108e2da663c4feeedd010c65954 imap-devel-2002d-12.ppc.rpm
d034338b4712651ab02d7ae40d4fd538 imap-utils-2002d-12.ppc.rpm

s390:
8e7c079ca5ec95e9767fbceb88403232 imap-2002d-12.s390.rpm
56dab9d88d5a7cf231da1b9321c62852 imap-devel-2002d-12.s390.rpm
10e343ab7ba2f7ba41b37309e8bd026e imap-utils-2002d-12.s390.rpm

s390x:
72f38762833f5f615b812b78bf5c0529 imap-2002d-12.s390x.rpm
c10832b30b30c614069e8be2bf062060 imap-devel-2002d-12.s390x.rpm
f23cdbc5a4a1c50375a36474dddabdd0 imap-utils-2002d-12.s390x.rpm

x86_64:
f90db06f0e5c48b220d071a698cec537 imap-2002d-12.x86_64.rpm
075645d561e9e7bac634d3f42855f6b4 imap-devel-2002d-12.x86_64.rpm
a4d5f9aad62c46de9d5b8fa4800402f2 imap-utils-2002d-12.x86_64.rpm

Red Hat Desktop version 3:

SRPMS:

ftp://updates.redhat.com/enterprise/3desktop/en/os/SRPMS/imap-2002d-12.src.rpm

8685e5bf17d4768f5254d8bd69debdf1 imap-2002d-12.src.rpm

i386:
7eef6e0ecc4147cc73a60be3e0d76647 imap-2002d-12.i386.rpm
820c2d446fd800cec6ce64ec2c42f494 imap-devel-2002d-12.i386.rpm
88d23ffc188f1d196d60ae43f7aa1939 imap-utils-2002d-12.i386.rpm

x86_64:
f90db06f0e5c48b220d071a698cec537 imap-2002d-12.x86_64.rpm
075645d561e9e7bac634d3f42855f6b4 imap-devel-2002d-12.x86_64.rpm
a4d5f9aad62c46de9d5b8fa4800402f2 imap-utils-2002d-12.x86_64.rpm

Red Hat Enterprise Linux ES version 3:

SRPMS:

ftp://updates.redhat.com/enterprise/3ES/en/os/SRPMS/imap-2002d-12.src.rpm

8685e5bf17d4768f5254d8bd69debdf1 imap-2002d-12.src.rpm

i386:
7eef6e0ecc4147cc73a60be3e0d76647 imap-2002d-12.i386.rpm
820c2d446fd800cec6ce64ec2c42f494 imap-devel-2002d-12.i386.rpm
88d23ffc188f1d196d60ae43f7aa1939 imap-utils-2002d-12.i386.rpm

ia64:
070f9e193a84fe7d67dd022eb98e4889 imap-2002d-12.ia64.rpm
6b5594df0491c151995d36ec5e88fd63 imap-devel-2002d-12.ia64.rpm
39b5b378efec1b4242c5b5a1ae188846 imap-utils-2002d-12.ia64.rpm

x86_64:
f90db06f0e5c48b220d071a698cec537 imap-2002d-12.x86_64.rpm
075645d561e9e7bac634d3f42855f6b4 imap-devel-2002d-12.x86_64.rpm
a4d5f9aad62c46de9d5b8fa4800402f2 imap-utils-2002d-12.x86_64.rpm

Red Hat Enterprise Linux WS version 3:

SRPMS:

ftp://updates.redhat.com/enterprise/3WS/en/os/SRPMS/imap-2002d-12.src.rpm

8685e5bf17d4768f5254d8bd69debdf1 imap-2002d-12.src.rpm

i386:
7eef6e0ecc4147cc73a60be3e0d76647 imap-2002d-12.i386.rpm
820c2d446fd800cec6ce64ec2c42f494 imap-devel-2002d-12.i386.rpm
88d23ffc188f1d196d60ae43f7aa1939 imap-utils-2002d-12.i386.rpm

ia64:
070f9e193a84fe7d67dd022eb98e4889 imap-2002d-12.ia64.rpm
6b5594df0491c151995d36ec5e88fd63 imap-devel-2002d-12.ia64.rpm
39b5b378efec1b4242c5b5a1ae188846 imap-utils-2002d-12.ia64.rpm

x86_64:
f90db06f0e5c48b220d071a698cec537 imap-2002d-12.x86_64.rpm
075645d561e9e7bac634d3f42855f6b4 imap-devel-2002d-12.x86_64.rpm
a4d5f9aad62c46de9d5b8fa4800402f2 imap-utils-2002d-12.x86_64.rpm

These packages are GPG signed by Red Hat for security. Our key
and details on how to verify the signature are available from
https://www.redhat.com/security/team/key/#package

7. References:

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2005-2933

8. Contact:

The Red Hat security contact is <secalert@redhat.com>. More
contact details at https://www.redhat.com/security/team/contact/

SUSE Linux

SUSE Security Announcement

Package: kernel
Announcement ID: SUSE-SA:2005:067
Date: Tue, 06 Dec 2005 13:00:00 +0000
Affected Products: SUSE LINUX 10.0
Vulnerability Type: denial of service
Severity (1-10): 6
SUSE Default Package: yes
Cross-References: CVE-2005-2973, CVE-2005-3044, CVE-2005-3055
CVE-2005-3180, CVE-2005-3181, CVE-2005-3271 CVE-2005-3527,
CVE-2005-3783, CVE-2005-3784 CVE-2005-3805, CVE-2005-3806,
CVE-2005-3807

Content of This Advisory:

Security Vulnerability Resolved: Various security fixes,
bugfixes and a XEN update Problem Description
Solution or Work-Around
Special Instructions and Notes
Package Location and Checksums
Pending Vulnerabilities, Solutions, and Work-Arounds: See SUSE
Security Summary Report.
Authenticity Verification and Additional Information

1) Problem Description and Brief Discussion

This kernel update for SUSE Linux 10.0 contains fixes for XEN,
various security fixes and bug fixes.

CVE-200n-nnnn numbers refer to Mitre CVE IDs (http://cve.mitre.org/).

This update includes a more recent snapshot of the upcoming XEN
3.0. Many bugs have been fixed. Stability for x86_64 has been
improved. Stability has been improved for SMP, and now both i586
and x86_64 kernels are built with SMP support.

This update contains the following security fixes:

CVE-2005-3783: A check in ptrace(2) handling that finds out if
a process is attaching to itself was incorrect and could be used by
a local attacker to crash the machine.
CVE-2005-3784: A check in reaping of terminating child
processes did not consider ptrace(2) attached processes and would
leave a ptrace reference dangling. This could lead to a local user
being able to crash the machine.
CVE-2005-3271: A task leak problem when releasing POSIX timers
was fixed. This could lead to local users causing a local denial of
service by exhausting system memory.
CVE-2005-3805: A locking problem in POSIX timer handling could
be used by a local attacker on a SMP system to deadlock the
machine.
CVE-2005-3181: A problem in the Linux auditing code could lead
to a memory leak which finally could exhaust system memory of a
machine.
CVE-2005-2973: An infinite loop in the IPv6 UDP loopback
handling can be easily triggered by a local user and lead to a
denial of service.
CVE-2005-3806: A bug in IPv6 flow label handling code could be
used by a local attacker to free non-allocated memory and in turn
corrupt kernel memory and likely crash the machine.
CVE-2005-3807: A memory kernel leak in VFS lease handling can
exhaust the machine memory and so cause a local denial of service.
This is seen in regular Samba use and could also be triggered by
local attackers.
CVE-2005-3055: Unplugging an user space controlled USB device
with an URB pending in user space could crash the kernel. This can
be easily triggered by local attacker.
CVE-2005-3180: Fixed incorrect padding in Orinoco wireless
driver, which could expose kernel data to the air.
CVE-2005-3044: Missing sockfd_put() calls in routing_ioctl()
leaked file handles which in turn could exhaust system memory.
CVE-2005-3527: A race condition in do_coredump in signal.c
allows local users to cause a denial of service (machine hang) by
triggering a core dump in one thread while another thread has a
pending SIGSTOP.

Additionally the following non security bugs were fixed:

Fix NFS cache consistency races which could lead to data
corruption and crashes.
A kernel panic when loading the r8169 module without
powermanagment was fixed.
i386: A race condition in the power management module
powernow-k8 was fixed.
Special ELF binaries without DATA and BSS segments could not be
loaded due to too strict kernel checks.
Various bugs in the ALSA sound system were fixed.
A problem in IPv6 initialization with IPv6 disabled by policy
that could leave dangling kernel pointers around was fixed.
Added sis 965l support to the sis5513 ide driver.
Disabled C2/C3 power management states on all IBM R40e
BIOSes.
Fixed machine crash when switching the io-scheduler away from
CFQ.
Call reboot notifiers of power off to switch off certain
machines.
AMD64: Don’t use TSC for time keeping on AMD single socket dual
core systems.
Fixed the “treason uncloaked” kernel messages that were caused
by a stale pred_flags variable when the TCP snd_wnd changes.
USB floppy drive SAMSUNG SFD-321U/EP was detected 8 times.
CONFIG_ACPI_HOTKEY is not supportable yet according to Intel,
so we disabled it.
Disable ACPI on machines from before 2001 on all kernels
again.
USB: always export interface information for modalias.
Various iSCSI fixes.
Avoid a potential fs corruption on SMP systems.
i386: Increased number of CONFIG_SERIAL8250NR_UARTS to 8.
Fixed a data corruption in the MD device driver when the
delayed recovery is interrupted.
ahci: Don’t set SActive for non-NCQ commands. This could have
left the LED burning even for inactivity.
ppc: Handle GCC 4 generated relocations for 32bit memory access
in the module loader.
ppc: Removed a special case for ppc to use MAC from prom if CSR
is corrupt
CIFS: Made cifsd (kernel daemon for the CIFS filesystem)
suspend aware.
Fixed ACPI issues on an ASUS L5D.
IDE: Worked around power management problems.
Disable AMD TLB flush filter on i386/x86-64 (might help 3d
drivers)
Quiet down capacity reading from IDE CD when no media
inserted.
ACPI: Worked around undefined ZOO* objects on certain Acer
Aspire notebooks.
ACPI: Fixed Oops on pcc_acpi unloading.
ACPI: Fix hang in ACPI device scan on certain HP nx
Laptops.
Fixed a bug in ACL handling of tmpfs.
Fix time going twice as fast problem on ATI Xpress chip
sets.

2) Solution or Work-Around

None, please install the fixed packages.

3) Special Instructions and Notes

SPECIAL INSTALLATION INSTRUCTIONS

The following paragraphs guide you through the installation
process in a step-by-step fashion. The character sequence “****”
marks the beginning of a new paragraph. In some cases, the steps
outlined in a particular paragraph may or may not be applicable to
your situation. Therefore, make sure that you read through all of
the steps below before attempting any of these procedures. All of
the commands that need to be executed must be run as the superuser
‘root’. Each step relies on the steps before it to complete
successfully.

Step 1: Determine the needed kernel type.
Use the following command to determine which kind of kernel is
installed on your system:

rpm -qf –qf ‘%{name} ‘ /boot/vmlinuz
Step 2: Download the packages for your system.
Download the kernel RPM package for your distribution with the
name indicated by Step 1. Starting from SUSE LINUX 9.2, kernel
modules that are not free were moved to a separate package with the
suffix ‘-nongpl’ in its name. Download that package as well if you
rely on hardware that requires non-free drivers, such as some ISDN
adapters. The list of all kernel RPM packages is appended
below.

The kernel-source package does not contain a binary kernel in
bootable form. Instead, it contains the sources that correspond
with the binary kernel RPM packages. This package is required to
build third party add-on modules.
Step 3: Verify authenticity of the packages.
Verify the authenticity of the kernel RPM package using the
methods as listed in Section 6 of this SUSE Security
Announcement.
Step 4: Installing your kernel rpm package.
Install the rpm package that you have downloaded in Step 2 with
the command

rpm -Uhv <FILE> replacing <FILE> with the filename
of the RPM package downloaded.

Warning: After performing this step, your system may not boot
unless the following steps have been followed completely.
Step 5: Configuring and creating the initrd.
The initrd is a RAM disk that is loaded into the memory of your
system together with the kernel boot image by the boot loader. The
kernel uses the content of this RAM disk to execute commands that
must be run before the kernel can mount its root file system. The
initrd is typically used to load hard disk controller drivers and
file system modules. The variable INITRD_MODULES in
/etc/sysconfig/kernel determines which kernel modules are loaded in
the initrd.

After a new kernel rpm has been installed, the initrd must be
recreated to include the updated kernel modules. Usually this
happens automatically when installing the kernel rpm. If creating
the initrd fails for some reason, manually run the command

/sbin/mkinitrd
Step 6: Update the boot loader, if necessary.
Depending on your software configuration, you either have the
LILO or GRUB boot loader installed and initialized on your system.
Use the command

grep LOADER_TYPE /etc/sysconfig/bootloader

to find out which boot loader is configured.

The GRUB boot loader does not require any further action after a
new kernel has been installed. You may proceed to the next step if
you are using GRUB.

If you use the LILO boot loader, lilo must be run to
reinitialize the boot sector of the hard disk. Usually this happens
automatically when installing the kernel RPM. In case this step
fails, run the command

/sbin/lilo

Warning: An improperly installed boot loader will render your
system unbootable.
Step 7: Reboot.
If all of the steps above have been successfully completed on
your system, the new kernel including the kernel modules and the
initrd are ready to boot. The system needs to be rebooted for the
changes to be active. Make sure that all steps have been completed
then reboot using the command

/sbin/shutdown -r now

Your system will now shut down and restart with the new
kernel.

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 <file.rpm>

to apply the update, replacing <file.rpm> with the
filename of the downloaded RPM package.

x86 Platform:

Power PC Platform:

SUSE LINUX 10.0:
   ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/ppc/kernel-default-2.6.13-15.7.ppc.rpm
b5b4e1ad4db39e8bede52cd0f171c508
   ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/ppc/kernel-iseries64-2.6.13-15.7.ppc.rpm
a7fbffd1f09d4e6c9a58950fe1692361
   ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/ppc/kernel-ppc64-2.6.13-15.7.ppc.rpm
a09e0b94d50c24ea8065b709ccb53775
   ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/ppc/kernel-source-2.6.13-15.7.ppc.rpm
ae4c7ad291aaa37dceb43e331651b2c4
   ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/ppc/kernel-syms-2.6.13-15.7.ppc.rpm
51ddc5ea24587d210edb3e249b0472c9

x86-64 Platform:

Sources:

SUSE LINUX 10.0:
   ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/src/Intel-536ep-4.69-14.2.src.rpm
c4ee0c5893efbde6ecf45f0da05e5103
   ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/src/kernel-source-2.6.13-15.7.src.rpm
56dd71a804ebcaa1eb8268665dfa2b18
   ftp://ftp.suse.com/pub/suse/i386/update/10.0/rpm/src/xen-3.0_7608-2.1.src.rpm
3571ce3e27ca472bffc2f2794eeae8a0

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 <file>

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

gpg: Signature made <DATE> using RSA key ID 3D25D3D9
gpg: Good signature from “SuSE Security Team <security@suse.de>”

where <DATE> 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
The internal rpm package signatures provide an easy way to
verify the authenticity of an RPM package. Use the command
rpm -v –checksig <file.rpm>

to verify the signature of the package, replacing
<file.rpm> 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.
If you need an alternative means of verification, use the
md5sum
command to verify the authenticity of the packages. Execute the
command

md5sum <filename.rpm>

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
<

Advisories, December 6, 2005

Fedora Core

Red Hat Linux

SUSE Linux

SPECIAL INSTALLATION INSTRUCTIONS

Web Webster

Recommended for you...

Company

Categories