-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
______________________________________________________________________________
SUSE Security Announcement
Package: binutils,kdelibs3,kdegraphics3,koffice,dia,lyx
Announcement ID: SUSE-SA:2006:007
Date: Fri, 10 Feb 2006 15:00:00 +0000
Affected Products: Novell Linux Desktop 9
SUSE LINUX 10.0
SUSE LINUX 9.3
SUSE LINUX 9.2
SUSE LINUX 9.1
SUSE SLES 9
Vulnerability Type: local privilege escalation
Severity (1-10): 6
SUSE Default Package: yes
Cross-References: -
Content of This Advisory:
1) Security Vulnerability Resolved:
privilege escalation due to empty RPATH in binaries
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
A SUSE specific patch to the GNU linker 'ld' removes redundant RPATH
and RUNPATH components when linking binaries.
Due to a bug in this routine ld occasionally left empty RPATH
components. When running a binary with empty RPATH components the
dynamic linker tries to load shared libraries from the current
directory.
By tricking users into running an affected application in a
directory that contains a specially crafted shared library an
attacker could execute arbitrary code with the user id of the
victim.
2) Solution or Work-Around
Do not run affected binaries in directories that are writeable by
other users. It is recommended to install the update packages.
To fix self-compiled applications install the updated binutils
package and relink the application.
3) Special Instructions and Notes
Use 'objdump -p' to check whether a binary is affected. RPATH and
RUNPATH must not contain a colon that is not surrounded by path
names.
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:
5336c44f08baed1eb20e31672e376996
8fa8cadb9fc305648d809c43d078ee74
b04b5ea686bface4391d91b96a06b4b7
4be879313304f774cc0e0721b9a4ca52
f93207a11a661c6beac8620693ceeb26
bdcdbdfb5651faabb99493b861fda9b2
82a02e5e55613d7cd60df86fbbb2b050
68702ff3f54cca4d3e8c95fd1953b02b
SUSE LINUX 9.3:
4cdc297d2ddc398829356d8032d2c570
f8364afec78108dcb3bb089112c9e486
e8405aca4fb3ddf5a5fe38095891173f
1521df464699151917c5edebf7c0e9c8
d5f69e63936e044c7668453643ebdb8d
c6db7f1b79c54fdbfee5306fb06d327c
3986977230c6cf5e375652707599d086
13e39a04f8dcdb2235a4554a242c01d8
SUSE LINUX 9.2:
574a32932f442d6ae097c62e67a804bb
d3d6d553b0e3f1a1e44e67a1e79cc336
0f9f1a102d15103fee1d1e6c29f70148
1ee1f29003e5333d777699d6b89b80f1
dcf97cc31d22664de69e730f734479be
0e79d0489c8fe12b62964f3ab3c653a2
cec40000030a2db31d34bbe048581e9a
27b0c1bfa0b2a683483b7122b34523aa
0a22a4ff2245610205a2275e41cd154a
SUSE LINUX 9.1:
d499c31bbd95986a70673d8cb11b99f4
ff479907370e9848e78b2762395457e0
9cf5e0afd4a5650db22cbf8e4da9ba01
5c90bfeca61591ce396066a7bba4acc7
a1611b75579097aa3d0031818b7b6db6
26ce2b4076b945a3d9ecf8af0b83e1e6
8c595a2e37986a22a09848a1a128645a
c2d8945ce2d0607cf909d29f83262f4f
b36749d947eb47286f0a21922b491a70
Power PC Platform:
SUSE LINUX 10.0:
de1e858bf7dac44e8adc2a07a0fcf334
7a2769b5e3e7ec4af6350dc1d826e7c3
ceb289844025be2048fb86a671ef3d48
c94eed10ad637634db3b24f08d5c0c81
6f9aa4b7433345db9826580872438eb5
307bdaead8245a26a7b2b00572d290dc
fb1247f46a4414bda0ac48acb971c126
4a4d94290e692bf515690953df895155
x86-64 Platform:
SUSE LINUX 10.0:
07905bd004aff0e7f034fbf1839880e4
2808eb66106aac360659f314ce6b8e8e
b72daa5dd362a30acb9c9ee60076a432
90db781dfd39d8c046c42c3117d42d21
50c7e9bb81a223766f8a1b05e961f586
bd603d3147becf226534a12d58de9848
324124fb727c6133de4c63fc0d8b109a
04f44a7a9113053c11ea2897fea189d1
1232ac61554a53bb772e4ee03d4e75ef
a96fa42b4bc03ff15d951029f7606b7d
SUSE LINUX 9.3:
503efba51e385e61053e177cab67e111
c4ac261d7021cff6ce157365c75b659f
b3d2853ee0f65fdb0f771f597555fde7
92681909dd0d1374386f2a081609cd2f
5a2494c0e345a35631c22647ff426541
389b8d61c3776006c4f2389f60b3e3c1
11f247f28d1dfd1837b8e2f2774c2446
bbe654a9c69c7e110e1b7de14b498312
6d4db92e1305e20aa3337624c845bd30
7da490073d6190af2003687951622405
SUSE LINUX 9.2:
a97601f2e0d5dd4768cda24282b2f4d9
6047b8d9493c221302439e289726fbd2
88b9c13e88b013370ac411f2aaa19c19
d2f8eba01914b6dd3d05c27c468dcfb0
7b8f6fbb5a0a311c29e900877aebd9d7
8540ad7e2a46994313cfd3a2963463b8
2032b30bb43091c625baa1792716ae61
7fbd5512b3598157e80c60f0b2855878
7b5077bce547bcdd4576c6a541f90267
7c62d3a25c8623f156fb43c36468935e
2dc9fac20d13442b3b5302dc29fe9118
SUSE LINUX 9.1:
354087b9758e50f86497996b19eeec94
03659fbb7563826a87f7f94beb1c75a6
353ef4a09a8a80e2d64b4d427976ce45
56d31cb34a3837725df75308e0f88703
d1458dddfcffacdb5ef6f430c31c6119
e525803caa7c3dd617f3c5a9a0683ff0
4d3432e2ffc9765d425e69cdf315ba4f
e2abc0442f078a34c1ca8516579e3a50
02bd9d62e0d1c38f8f71f0cf2494b41b
e002a223ab2e3c024c0df5693fd1a3a8
08b03cb4214d760bf6072cd59aac5003
e4bc1e182a72bb3a9e4a878208f13cfe
Sources:
SUSE LINUX 10.0:
2dd1e35033820628da6b80be0dbe4936
0397a4c448a829ac21c11305212ff22b
7c198fa4ace4919c221939e6eca00734
SUSE LINUX 9.3:
98d6ea23959aea2765f9c17702ec62dd
e15f2a22a803a18be7a1ab145a25007b
aeeb36fc3937dd93d506f526c6c98cc4
SUSE LINUX 9.2:
952e90bdae6b1abeb7ca13b4401b398c
4f1d414bf9fd2a2515aaf4463a441aaa
0fae44a5765adc1de2b5462873560bfd
7debc7aeee1ffca646d5c7216ce683fe
SUSE LINUX 9.1:
5c7ab33f6c050ba300aaaba7e2040fb4
8ae65c3f8ab7d3edf8a4e24209ed9e64
851de1a4caea121c9ed82d77115928b5
239ff55c3e755403a97a121a058c2caf
309668f36903aed44e8bfd15435f1908
51ddd6ca60f542ad852eff7a436a7275
c23abf7c55209043d1c546877d2aaef7
d341d9f1e16966db09bd071aeece3a3b
029f7638dbcba4c841e3803121fb30c7
Our maintenance customers are notified individually. The packages are
offered for installation from the maintenance web:
https://www.suse.com:443/
https://www.suse.com:443/
https://www.suse.com:443/
https://www.suse.com:443/
______________________________________________________________________________
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.
====================================================================
