SUSE Security Announcement
Package: mozilla
Announcement-ID: SUSE-SA:2004:036
Date: Wednesday, Oct 6th 14:36:39 MEST 2004
Affected products: 8.1, 8.2, 9.0, 9.1 SUSE Linux Enterprise Server
8, 9 SUSE Linux Desktop 1.0
Vulnerability Type: various vulnerabilities
Severity (1-10): 5
SUSE default package: yes
Cross References: http://www.mozilla.org/security/
Content of this advisory:
- security vulnerability resolved:
- various vulnerabilities problem description
- solution/workaround
- special instructions and notes
- package location and checksums
- pending vulnerabilities, solutions, workarounds:
- openmotif
- standard appendix (further information)
1) problem description, brief discussion
During the last months a number of security problems have been
fixed in Mozilla and Mozilla based brwosers. These include:
- CAN-2004-0718: content in unrelated windows could be
modified - CAN-2004-0722: integer overflow in the SOAPParameter object
constructor - CAN-2004-0757: heap-based buffer overflow in the SendUidl of
POP3 code - CAN-2004-0758: denial-of-service with malicious SSL
certificates - CAN-2004-0759: read files via JavaScript
- CAN-2004-0760: MIME code handles %00 incorrectly
- CAN-2004-0761: spoofing of security lock icon
- CAN-2004-0762: manipulation of XPInstall Security dialog
box - CAN-2004-0763: spoofing of SSL certificates by using redirects
and JavaScript - CAN-2004-0764: hijacking the user interface via the “chrome”
flag and XML User Interface Language (XUL) files - CAN-2004-0765: spoofing SSL certificates due to incorrecting
comparsion of hostnames - CAN-2004-0902: Several heap based buffer overflows in Mozilla
Browsers. - CAN-2004-0903: Stack-based buffer overflow in the writeGroup
function in vcard handling. - CAN-2004-0904: Overflow in BMP bitmap decoding.
- CAN-2004-0905: Crossdomain scripting and possible code
execution by javascript drag and drop. - CAN-2004-0906: XPI Installer sets insecure permissions,
allowing local users to overwrite files of the user. - CAN-2004-0908: Allow untrusted javascript code to read and
write to the clipboard. - CAN-2004-0909: Allow remote attackers to trick the user into
performing dangerous operations by modifying security relevant
dialog boxes. 2) solution/workaround
Since there is no workaround, we recommend an update in any case
if you use the mozilla browser.
3) special instructions and notes
After successfully updating the package(s) you need to close all
instances of the web browser and restart it again.
4) package location and checksums
Due to the large amount of updated packages and dependencies we
do not provide MD5-sums this time. The updates are
cryptographically signed and are available for download via the
Yast Online Update.
5) Pending vulnerabilities in SUSE Distributions and
Workarounds:
- openmotif The XPM security problems within openmotif have been
fixed. New packages are available on our ftp servers.
6) standard appendix: authenticity verification, additional
information
- Package authenticity verification:
SUSE update packages are available on many mirror ftp servers
all over the world. While this service is being considered valuable
and important to the free and open source software community, many
users wish to be sure about the origin of the package and its
content before installing the package. There are two verification
methods that can be used independently from each other to prove the
authenticity of a downloaded file or rpm package:- md5sums as provided in the (cryptographically signed)
announcement. - using the internal gpg signatures of the rpm package.
- execute the command md5sum <name-of-the-file.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 announcement. Since the announcement containing the checksums
is cryptographically signed (usually using the key [email protected]), the checksums show
proof of the authenticity of the package. We disrecommend to
subscribe to security lists which cause the email message
containing the announcement to be modified so that the signature
does not match after transport through the mailing list software.
Downsides: You must be able to verify the authenticity of the
announcement in the first place. If RPM packages are being rebuilt
and a new version of a package is published on the ftp server, all
md5 sums for the files are useless. - 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, where
<file.rpm> is the filename of the rpm package that you have
downloaded. Of course, package authenticity verification can only
target an un-installed rpm package file. Prerequisites:- gpg is installed
- The package is signed using a certain key. The public part of
this key must be installed by the gpg program in the directory
~/.gnupg/ under the user’s home directory who performs the
signature verification (usually root). You can import the key that
is used by SUSE in rpm packages for SUSE Linux by saving this
announcement to a file (“announcement.txt”) and running the command
(do “su -” to be root): gpg –batch; gpg < announcement.txt |
gpg –import SUSE Linux distributions version 7.1 and thereafter
install the key “[email protected]”
upon installation or upgrade, provided that the package gpg is
installed. The file containing the public key is placed at the
top-level directory of the first CD (pubring.gpg) and at ftp://ftp.suse.com/pub/suse/pubring.gpg-build.suse.de
.
- md5sums as provided in the (cryptographically signed)
- SUSE runs two security mailing lists to which any interested
party may subscribe: [email protected] - general/linux/SUSE security discussion. All SUSE security
announcements are sent to this list. To subscribe, send an email to - SUSE’s announce-only mailing list. Only SUSE’s security
announcements are sent to this list. To subscribe, send an email toFor general information or the frequently asked questions (faq)
send mail to:<[email protected]>
or <[email protected]>
respectively.
SUSE’s security contact is <[email protected]> or
<[email protected]>. The
<[email protected]>
public key is listed below.
The information in this advisory may be distributed or
reproduced, provided that the advisory is not modified in any way.
In particular, it is desired that the clear-text signature shows
proof of the authenticity of the text.
SUSE Linux AG makes no warranties of any kind whatsoever with
respect to the information contained in this security advisory.
Type Bits/KeyID Date User ID
pub 2048R/3D25D3D9 1999-03-06 SuSE Security Team <[email protected]>
pub 1024D/9C800ACA 2000-10-19 SuSE Package Signing Key <[email protected]>
SUSE Security Announcement
Package: samba
Announcement-ID: SUSE-SA:2004:035
Date: Tuesday, Oct 5th 2004 16:53:01 MEST
Affected products: 8.1, 8.2, 9.0 SUSE Linux Enterprise Server 8
SUSE Linux Desktop 1.0
Vulnerability Type: remote file disclosure
Severity (1-10): 6
SUSE default package: Yes
Cross References: CAN-2004-0815
Content of this advisory:
- security vulnerability resolved:
- Samba file access problem problem description
- solution/workaround
- special instructions and notes
- package location and checksums
- pending vulnerabilities, solutions, workarounds:
- opera
- kernel
- mozilla
- standard appendix (further information)
1) problem description, brief discussion
The Samba server, which allows to share files and resources via
the SMB/CIFS protocol, contains a bug in the sanitation code of
path names which allows remote attackers to access files outside of
the defined share. In order to access these files, they must be
readable by the account used for the SMB session. CAN-2004-0815 has
been assigned to this issue.
2) solution/workaround
As a temporary workaround you can set the wide links = no
option in smb.conf and restart the samba server. However an update
is recommended nevertheless.
3) special instructions and notes
After successfully updating the samba package, you need to issue
the following command as root:
rcsmb restart
4) package location and checksums
Please download the update package for your distribution and
verify its integrity by the methods listed in section 3) of this
announcement. Then, install the package using the command “rpm -Fhv
file.rpm” to apply the update.
Our maintenance customers are being notified individually. The
packages are being offered to install from the maintenance web.
SUSE Linux 9.0:
ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/samba-2.2.8a-226.i586.rpm
eb71869029b35d2a97d55e26514524db
patch rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/samba-2.2.8a-226.i586.patch.rpm
48bb3e455079fcfdf4ad2baa28f28557
source rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/samba-2.2.8a-226.src.rpm
d162ea5a39b14ee16ae1c6d5df9211bb
SUSE Linux 8.2:
ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/samba-2.2.8a-225.i586.rpm
79b0514a827bdd782e6d3f62bb92fb85
patch rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/samba-2.2.8a-225.i586.patch.rpm
a50dd448212245d51e9ac59ae50514e8
source rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/samba-2.2.8a-225.src.rpm
25d488678b607b3c67612ee065abd77a
SUSE Linux 8.1:
ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/samba-2.2.8a-224.i586.rpm
93d0fb2502f30593548dbe2f41ec8948
patch rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/samba-2.2.8a-224.i586.patch.rpm
da5b107fb71c5daf5972b6e0aaca4f5c
source rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/samba-2.2.8a-224.src.rpm
e0b9f9af6c5348cb9840b5d98a1c59dc
x86-64 Platform:
SUSE Linux 9.0:
ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/samba-2.2.8a-226.x86_64.rpm
0f1c94aa23653b0cf9b318646d9153af
patch rpm(s):
ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/samba-2.2.8a-226.x86_64.patch.rpm
569974c359702c263b0968ce8fb9810f
source rpm(s):
ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/src/samba-2.2.8a-226.src.rpm
75c1a01d03af42835809691840eaa331
5) Pending vulnerabilities in SUSE Distributions and
Workarounds:
- opera
New opera packages are available on our ftp servers, fixing
CAN-2004-0691, CAN-2004-0597, CAN-2004-0598, CAN-2004-0599 and
CAN-2004-0746. - kernel
Update kernels for the kNFSd problem for SLES 8 and SL 8.1 have
been released. - mozilla
We are in the process of releasing updates for mozilla (and related
browsers), fixing various issues: CAN-2004-0597, CAN-2004-0718,
CAN-2004-0722, CAN-2004-0757, CAN-2004-0758, CAN-2004-0759,
CAN-2004-0760, CAN-2004-0761, CAN-2004-0762, CAN-2004-0763,
CAN-2004-0764 and CAN-2004-0765. We will give you concrete details
in a separate mozilla advisory when the updates are available.
6) standard appendix: authenticity verification, additional
information
- Package authenticity verification:
SUSE update packages are available on many mirror ftp servers
all over the world. While this service is being considered valuable
and important to the free and open source software community, many
users wish to be sure about the origin of the package and its
content before installing the package. There are two verification
methods that can be used independently from each other to prove the
authenticity of a downloaded file or rpm package:- md5sums as provided in the (cryptographically signed)
announcement. - using the internal gpg signatures of the rpm package.
- execute the command md5sum <name-of-the-file.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 announcement. Since the announcement containing the checksums
is cryptographically signed (usually using the key [email protected]), the checksums show
proof of the authenticity of the package. We disrecommend to
subscribe to security lists which cause the email message
containing the announcement to be modified so that the signature
does not match after transport through the mailing list software.
Downsides: You must be able to verify the authenticity of the
announcement in the first place. If RPM packages are being rebuilt
and a new version of a package is published on the ftp server, all
md5 sums for the files are useless. - 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, where
<file.rpm> is the filename of the rpm package that you have
downloaded. Of course, package authenticity verification can only
target an un-installed rpm package file. Prerequisites:- gpg is installed
- The package is signed using a certain key. The public part of
this key must be installed by the gpg program in the directory
~/.gnupg/ under the user’s home directory who performs the
signature verification (usually root). You can import the key that
is used by SUSE in rpm packages for SUSE Linux by saving this
announcement to a file (“announcement.txt”) and running the command
(do “su -” to be root): gpg –batch; gpg < announcement.txt |
gpg –import SUSE Linux distributions version 7.1 and thereafter
install the key “[email protected]”
upon installation or upgrade, provided that the package gpg is
installed. The file containing the public key is placed at the
top-level directory of the first CD (pubring.gpg) and at ftp://ftp.suse.com/pub/suse/pubring.gpg-build.suse.de
.
- md5sums as provided in the (cryptographically signed)
- SUSE runs two security mailing lists to which any interested
party may subscribe: - general/linux/SUSE security discussion. All SUSE security
announcements are sent to this list. To subscribe, send an email to - SUSE’s announce-only mailing list. Only SUSE’s security
announcements are sent to this list. To subscribe, send an email toFor general information or the frequently asked questions (faq)
send mail to:<[email protected]>
or <[email protected]>
respectively.
SUSE’s security contact is <[email protected]> or
<[email protected]>. The
<[email protected]>
public key is listed below.
The information in this advisory may be distributed or
reproduced, provided that the advisory is not modified in any way.
In particular, it is desired that the clear-text signature shows
proof of the authenticity of the text.
SUSE Linux AG makes no warranties of any kind whatsoever with
respect to the information contained in this security advisory.
Type Bits/KeyID Date User ID
pub 2048R/3D25D3D9 1999-03-06 SuSE Security Team <[email protected]>
pub 1024D/9C800ACA 2000-10-19 SuSE Package Signing Key <[email protected]>