-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
______________________________________________________________________________
SUSE Security Announcement
Package: mozilla,MozillaFirefox,MozillaThunderbird
Announcement ID: SUSE-SA:2007:036
Date: Wed, 27 Jun 2007 15:00:00 +0000
Affected Products: SUSE LINUX 10.0
SUSE LINUX 10.1
openSUSE 10.2
UnitedLinux 1.0
SuSE Linux Enterprise Server 8
SuSE Linux Openexchange Server 4
SuSE Linux Standard Server 8
SuSE Linux School Server
SUSE LINUX Retail Solution 8
SUSE SLES 9
Novell Linux Desktop 9
Open Enterprise Server
Novell Linux POS 9
SUSE Linux Enterprise Desktop 10 SP1
SUSE Linux Enterprise Server 10 SP1
Vulnerability Type: remote code execution
Severity (1-10): 7
SUSE Default Package: yes
Cross-References: CVE-2007-1362, CVE-2007-1558, CVE-2007-1562
CVE-2007-2867, CVE-2007-2868, CVE-2007-2869
CVE-2007-2870, CVE-2007-2871, MFSA 2007-11
MFSA 2007-12, MFSA 2007-13, MFSA 2007-14
MFSA 2007-15, MFSA 2007-16, MFSA 2007-17
Content of This Advisory:
1) Security Vulnerability Resolved:
Mozilla security problems
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
Various Mozilla family browsers have been updated to their current
security release versions.
The Mozilla Seamonkey suite was brought to security update version
1.0.9.
The Mozilla Firefox browser was brought to security update version
1.5.0.12 on Novell Linux Desktop 9 and 2.0.0.4 on SUSE Linux Enterprise
10, SUSE Linux 10.0, 10.1 and openSUSE 10.2.
The Mozilla Thunderbird mailreader was brought to security update
version 1.5.0.12 on SUSE Linux 10.0, 10.1 and openSUSE 10.2.
Note that most of the packages were released some weeks ago already,
only MozillaFirefox for SLE10 Service Pack 1 was missing and released
today.
The following security issues have been fixed:
- MFSA 2007-17 / CVE-2007-2871:
Chris Thomas demonstrated that XUL popups opened by web content
could be placed outside the boundaries of the content area. This
could be used to spoof or hide parts of the browser chrome such as
the location bar.
- MFSA 2007-16 / CVE-2007-2870:
Mozilla contributor moz_bug_r_a4 demonstrated that the
addEventListener method could be used to inject script into another
site in violation of the browser's same-origin policy. This could
be used to access or modify private or valuable information from
that other site.
- MFSA 2007-15 / CVE-2007-1558:
Gaëtan Leurent informed us of a weakness in APOP authentication
that could allow an attacker to recover the first part of your mail
password if the attacker could interpose a malicious mail server on
your network masquerading as your legitimate mail server. With normal
settings it could take several hours for the attacker to gather
enough data to recover just a few characters of the password. This
result was presented at the Fast Software Encryption 2007 conference.
- MFSA 2007-14 / CVE-2007-1362:
Nicolas Derouet reported two problems with cookie handling in
Mozilla clients. Insufficient length checks could be use to exhaust
browser memory and so to crash the browser or at least slow it done
by a large degree.
The second issue was that the cookie path and name values were not
checked for the presence of the delimiter used for internal cookie
storage, and if present this confused future interpretation of the
cookie data. This is not considered to be exploitable.
- MFSA 2007-13 / CVE-2007-2869:
Marcel reported that a malicious web page could perform a denial
of service attack against the form autocomplete feature that would
persist from session to session until the malicious form data
was deleted. Filling a text field with millions of characters and
submitting the form will cause the victim's browser to hang for up
to several minutes while the form data is read, and this will happen
the first time autocomplete is triggered after every browser restart.
No harm is done to the user's computer, but the frustration caused
by the hang could prevent use of Thunderbird if users don't know
how to clear the bad state.
- MFSA 2007-12 / CVE-2007-2867 / CVE-2007-2868
As part of the Thunderbird 2.0.0.4 and 1.5.0.12 update releases
Mozilla developers fixed many bugs to improve the stability of
the product. Some of these crashes that 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.
Without further investigation we cannot rule out the possibility
that for some of these an attacker might be able to prepare memory
for exploitation through some means other than JavaScript, such as
large images.
- MFSA 2007-11 / CVE-2007-1562:
Incorrect FTP PASV handling could be used by malicious ftp servers to do a rudimentary port scanning of for instance internal networks
of the computer the browser is running on.
2) Solution or Work-Around
There is no known workaround, please install the update packages.
3) Special Instructions and Notes
Please restart running instances of the Mozilla browsers.
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 10.2:
f0934f90b9b1317cd4fde6f7283cb354
477431b4794d05c1efb50450b621c8cc
3de3e5a53878000c607328976321bce5
1b5d7f610238e4aa3bfd60b83719df2d
a49ae41f41889ed3f95cc9e06d973f0a
0e19cbdb8265f6d694af0b051a2d0896
c10c9c6c19bf70bc1ae09432dafaa96a
9e188480b49becde5c7cb5aa11014b7f
e5136aecd49e521d68b132cfc41ece95
f73c8976ab4e150c703aa34a52b4485d
SUSE LINUX 10.1:
29a0235bf253cfba50b5d49f23a0ec4a
6e8f11558a5e574f77b62a271cf5c9d8
3f83847ddf92da3d4ad9631eeb85ba19
c90a3696906c9d714a2e200ce4258f7b
6cf0ec81f12c45a905e494c21ea78441
8e01c1563ee640bf486285677d94758d
dd2330f0c7c6242bc7ca1cf438991eaa
1f7047eca4842ed1cab60bff171063ce
910edcadcad6643fc291b0063682844a
SUSE LINUX 10.0:
19191dc672c70531f82e31e790a3fd45
03df32401f0d26fdb3b1f1f0ae81fc04
d5b6b6efe54bc1f8f6a69eb6539d7f93
e67bbb6492ff7126bfa3f1a0e9558754
0701d27f3b9302af5a36cb9bd45a8d1f
37186235502620f95aba619ae5d7cf8f
38d2e3863af12395581fe2a1324c84e8
67b2bac56505ef5e5c4855e3d08e902d
6ec8abbe514b20e056ba0a002e572495
6f06f6f190a5c1c49f8d81f18d9ff764
133292741f3846d8fc3a690631f6eec8
cd919366cb097546e2ee38528d6dc901
b630ace9d7f004f492586d0a743f5c38
252959495c13b3e0ae3db2f4a60152fa
Power PC Platform:
openSUSE 10.2:
8bdbf5747caac7d8eadfcd699a8df876
93bddb126429b0ad45b33ba2e634c6eb
9e65077db02c442110b84d1b9d4686d7
dda551a38752d5ea85f9c409101f9191
d5d6472b0f9072eeacd96eeae4066244
def55111829f6e44c1014629afc71c4b
f8249136cf999c1e2d0c041d38f50f8f
155356604d1aa69a1fd820db1673d1b5
44e5e6121c374291647679b57b8bd14e
0ba59f4c2052134b724d367b1d03023e
SUSE LINUX 10.1:
6949a54dc88703fff895e90e0520bef9
da04bee9642a2df6a134d7be4cd3d035
1a57483c12edd4441f65a4ccdb513ef3
4b5bcc76122bb0072ff19d25f476c6de
3edf23d1784de11ea412de7f1aaebda6
58ef7b10f710dd37c27f2a02035c4694
8395dde13959dec487edf86f6ce325ed
75e87dbc39db69384e9f45cd683ce5e0
1a418b0a27c29435357f1566aa4f5316
SUSE LINUX 10.0:
96d8813f7db159289729c60d197a9e5d
5297527f3321f6ca041ccbc9f36642a7
3881d9c68d0267d4e9249d06b826a44d
72877090914acfd87f46aef0faea82c2
bc23dff33ea37a9e97837ece4d52b233
9b744a729a813e8b38244b6526c1914a
1fce4602f57d3be5057aa414d5282e9e
51fdd891f1a6e16d0ade4820ff2fedc3
035eabc425e81c85ff8cb0d6dd02a68c
987f878b3cf8e748b8ed27ae73287708
88f76c724fcc3f513b88b85921de5c34
442e84c4943ef6c942e53975385f678c
43e4d47d42dabf5cd2abc9d6d4364437
42a78d68b32a01b609745d974ef801de
x86-64 Platform:
openSUSE 10.2:
c3ca2ab48d0b99dd7fb9f8c472e42747
60ced8199dd3f92f8595a4d91bab75b6
80ee951627791441458b891038627be7
40acbb81b9ea3407523bb6c3492be0ef
1bab178914365c05b36e0c0b0568a0be
a595cec31ec16184eca0beb77cebfec5
bbd28d28373023b37b9b30bd795c2ec8
43ef6fea3d291ca0e04515b60871ccad
e241f97f46061f6f21974d05bc1b50cf
ac1923a3b07fdce0e3a6be5aa31ec820
SUSE LINUX 10.1:
0855522ab6c4445dc40a764baa8422bb
782189e8cf043d733574c51230d3558c
a2670116510c10ec57c7b7f2fc21f85a
72a95a37d4492932ac433c2ea952ac0b
b9e46aaf2f41a71f8663df8b3fd304d9
44afaa26ae3a193a289636fe83265573
7409a8e3835eb9fa96fc44ce0cd79c0a
5fa598537da5435a93d580f2cb30e409
b5a7fefd3d0414676f54d28c91a7c6e0
SUSE LINUX 10.0:
24b839f20854f85ed5c46cc521dd3e52
cd78f077f8edd9bd53aec4ecfb3458cb
c3b246702992a8ca436362fca091df3f
a1a78ea192b84c48ffc88537f7c73e1c
314a69dd24403c885bd5637e062c8e3b
34e836368c3af95f2ed6fb29483d7f65
f5b21cb007c78981e4378db7646addda
67e4bf609a8c70660ac87383a9c748f4
eb3d340b84068fe10ba4ffe5087898a0
cb54d16f054aa90c095b9fe5fccc6ffd
f33d2cea73d1af5e1cb83177b8deac73
ae82f6f8930b389385896032913425dd
Sources:
openSUSE 10.2:
5b8cc0328993e0f1e9e5d5170bad3cf8
5108a0596afc62d55f3b947ecbe1f688
576b5d0bc8639eb701617f4e205d61d4
SUSE LINUX 10.1:
250e065587d29b9b2c5f7e0ab316dff0
dce615a3b1eaedae46811ae232820c4b
SUSE LINUX 10.0:
4623d81fe310e6b8500cc90d641ea66e
1d6cb946b6887d8bb90c2013b4f99b57
20950f97fff97455295637ee2146e452
ffefb87fbb42e485fe9b4fd2dbc7073f
e10f948d05e1195e6cd8380b0dcc267a
19f1b77f3023a7c33a85168e775f0fee
Our maintenance customers are notified individually. The packages are
offered for installation from the maintenance web:
Open Enterprise Server
Novell Linux POS 9
SUSE SLES 9
http://support.novell.com/techcenter/psdb/2b5bd41bb32a85566962cdcd145ebc9c.html
SUSE Linux Enterprise Server 10 SP1
SUSE Linux Enterprise Desktop 10 SP1
http://support.novell.com/techcenter/psdb/79d4c8b0ac0295ba7a79cbb3f332f569.html
Novell Linux Desktop 9
http://support.novell.com/techcenter/psdb/2b5bd41bb32a85566962cdcd145ebc9c.html
http://support.novell.com/techcenter/psdb/27f238ef9f4330d0baa92f474b175c68.html
http://support.novell.com/techcenter/psdb/f91eb16b534b592433bff9cd13cddd43.html
Novell Linux Desktop 9 for x86
http://support.novell.com/techcenter/psdb/f91eb16b534b592433bff9cd13cddd43.html
UnitedLinux 1.0
SuSE Linux Openexchange Server 4
SuSE Linux Enterprise Server 8
SuSE Linux Standard Server 8
SuSE Linux School Server
SUSE LINUX Retail Solution 8
http://support.novell.com/techcenter/psdb/82350c13101121c9602342904dd755b6.html
______________________________________________________________________________
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.
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:
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
.
==================================================================== SUSE's security contact is or .
The public key is listed below.
====================================================================