-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
______________________________________________________________________________
SUSE Security Announcement
Package: nfs-server
Announcement ID: SUSE-SA:2006:005
Date: Thu, 26 Jan 2006 14:00:00 +0000
Affected Products: SUSE LINUX 10.0
SUSE LINUX 9.3
SUSE LINUX 9.2
SUSE LINUX 9.1
Vulnerability Type: remote code execution
Severity (1-10): 7
SUSE Default Package: no
Cross-References: CVE-2006-0043
Content of This Advisory:
1) Security Vulnerability Resolved:
remote code execution in rpc.mountd of nfs-server
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
An remotely exploitable problem exists in the rpc.mountd service in
the user space NFS server package "nfs-server".
Insufficient buffer space supplied to the realpath() function
when processing mount requests can lead to a buffer overflow in
the rpc.mountd and allows remote attackers to execute code as the
root user.
Code execution is definitely possible if the attacker can create
symlinks on any of the file systems on the machine running rpc.mountd
(/tmp , /home/attacker or similar).
For attackers without filesystem access code execution is potentially
possible.
NOTE:
The "nfs-server" package is obsolete and has been replaced by the
"nfs-utils" package (kernel NFS server) in all currently supported
SUSE Linux products already and is only included for completeness.
The "nfs-utils" package itself is NOT affected by this problem.
This issue is tracked by the Mitre CVE ID CVE-2006-0043.
2) Solution or Work-Around
If you are still using the old user space nfs-server package, consider
switching to the kernel level nfs-utils package which is not affected
by this problem.
If you are not using NFS serving at all, deinstall the RPM.
Otherwise install the updated packages.
3) Special Instructions and Notes
None.
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 10.0:
5e37fe16b2c59ecd4f5296ab63710080
SUSE LINUX 9.3:
12d423a4df41149131c184ba98cd139f
SUSE LINUX 9.2:
4df2803717ec4404204f2550c3aa8240
SUSE LINUX 9.1:
0e4b9814cfc427d708ed664fcb2d5e83
Power PC Platform:
SUSE LINUX 10.0:
e64aa29d0b1cdbf8c7801592df9bf199
x86-64 Platform:
SUSE LINUX 10.0:
961bef35240193e56c5f3bf6828611c8
SUSE LINUX 9.3:
8cacbd583e70f204897f5f4449f4dedd
SUSE LINUX 9.2:
24a0186b5f57fadd1fb7753e416d3d2a
SUSE LINUX 9.1:
33b5dddc7a9e717fa229661efa9592d5
Sources:
SUSE LINUX 10.0:
2fc9d81e214d444cb305f8a485930a48
SUSE LINUX 9.3:
3d21171dda052e1e744d08ba7dd39742
SUSE LINUX 9.2:
0f7c7a1eea16a9eb1c444c54805d9ccd
SUSE LINUX 9.1:
e88cb3eae24d151197fc2a3e7731fd71
bceb7a43b4ad42cec21be4da14988d45
______________________________________________________________________________
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:
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.
====================================================================
