Stay Secure with the Latest Linux Advisories

security advisorymoderateupdate

SUSE 2006-073 Moderate: Code Execution Risk in Mono Local Escalation

Sebastian Krahmer of SUSE Security found that the Mono Sebastian Krahmer of SUSE Security found that the Mono System.Xml.Serialization class contained a /tmp race which potentially System.Xml.Serialization class contained a /tmp race which potentially allows local attackers to execute code as the user using the Serialization method. This is tracked by the Mitre CVE ID CVE-2006-5072.. -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ______________________________________________________________________________ SUSE Security Announcement Package: mono-core Announcement ID: SUSE-SA:2006:073 Date: Fri, 01 Dec 2006 16:00:00 +0000 Affected Products: Novell Linux Desktop 9 Open Enterprise Server SLE SDK 10 SLES SDK 9 SUSE LINUX 10.1 SUSE LINUX 10.0 SUSE LINUX 9.3 SUSE SLED 10 SUSE SLES 10 Vulnerability Type: local privilege escalation Severity (1-10): 5 SUSE Default Package: yes Cross-References: CVE-2006-4799, CVE-2006-4800, CVE-2006-5072 CVE-2006-5973 Content of This Advisory: 1) Security Vulnerability Resolved: Mono tempfile race might lead to privilege escalation Problem Description 2) Solution or Work-Around 3) Special Instructions and Notes 4) Package Location and Checksums 5) Pending Vulnerabilities, Solutions, and Work-Arounds: - dovecot off by one overflow - xine-lib several overflows - kdegraphics3 kfile_jpeg EXIF crashes 6) Authenticity Verification and Additional Information ______________________________________________________________________________ 1)Problem Description and Brief Discussion Sebastian Krahmer of SUSE Security found that the Mono System.Xml.Serialization class contained a /tmp race which potentially allows local attackers to execute code as the user using the Serialization method. This is tracked by the Mitre CVE ID CVE-2006-5072. Packages for all affected distributions were released on November 10th, and for SLE 10 on November 27th. 2) Solution or Work-Around There is no known workaround, please install the update packages. 3) Special Instructions and Notes Please close and restart all running instances of beagle (one user of C# serialization) after the update. 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.1: 7b4abac64336eb30d5937b25aabe7494 66859d556f70601ca9b73d7b401f6985 02b60b74291d274e763f90d34db1541f 9036159cfa23d2d87434c053cf7d8999 eb618bb94e3fe4ffedb155cb2c213624 d02343e65f86dbbe12b29196bb5fdf2c d64bc8dd2687a516aadd13b3c554ea95 a80d59f87ec8c37f339014485e4a39d4 dceba155389e2427ae71fa0997142842 09d51fa450bacc0eea814c32c5dcbec5 3f57ef06657bac839837fefeef45b0ec 83b41f4bdfb04e8ee7afd0ef0796aa17 aeb8b0d7490918bfb4777f1d472529e9 6715990b4674d06897929e892758d656 eb37fcf30228a1e3a4be1030f02d163d cf507f8fb0d351ee109acfbcf742af2f 36e253dceff26c6d8665842d2092d2a8 SUSE LINUX 10.0: 8723e97076ed998aedb5c149745a4240 82a201ed72c8ccf6e564063b036756f6 e6b5ea2f15319e9bbf7f06bbdd564af5 a2cb5556848cd0dfa9ad8eae3f4c4eb2 e96d50f8c57e97f01b09bf45df6d5caa ec79d94d2c77199fcda0e0a1b345e79e 1725efd5f7231007cbafde6dbb17d6d3 defe0b0095be00f5db4ce6a68e0768da 0935ede50fd97451dceca2429a94b69c f64733249eaa4cfdcb5bc18da199136b f85c62aca21da3c246487e7acaa46279 6297e9c7666b6982b8f2fe681b65eeb5 f81c3d2f2e4cb78923fe97c476f51f8e f5364d8503d3b0224a02602db6fd3ac2 ecda8771dd681ea6b59c5299e0feaf02 ea5b6cf547461a7dd0acbabd6f1c6e5f SUSE LINUX 9.3: 1a547c3c0ab97e5055ceaf3d31dbdb3a 087cdd86b5f7b5d9cbbda2a2f9d27bd1 3b423876c8143c012431810d56d5efbc 58345dff171b360a90ff551e9d41af8b c2f4a478f0b6e928b1ceaec1be0b9471 44470ab6051edcd175463cdd891729ce 01df17ef51f4dd2ca09720ddfabc2479 412e9c9b7e1c1a34484242cab4cad458 19e03e53d58589369fdebb168d7a73f1 c310e0e401f7c6e199c8da324b9ffd9d 3a21f822e56267d0b9f4401430e96abb 4f5667eacc74fda44bd90d4f3e9c337e 8a53abf982e0d1b0ca85bba71ec65635 c458032d6863a1f1eab9a020031e735a 308768cbcf198fa1ec3172e26e9d67d1 Power PC Platform: SUSE LINUX 10.1: 9313cea2c9dec8f52cdfe4441248ee54 a9e6e92384d55db7ab84498997ff95b5 c5d31bd0f0897a093d058efb3e9d36ee 5f08a5f5ceed82e3a2029af9fe44243e c77b18deac849e205a686140dc577077 096347d6190bbd6952f34a06191c0b5b 068132b00bf66578afd0f57a02fbc0f3 a7633423935807d8ec63af34c140126f 7d679cd2374a89c3def920368bbcd689 19ebb43356078a17b7e962db58ac8058 8274b40f614ab66d8e588f284a1e654b abd9e49ffaaabb50d9e9dfdc7c02bf2a 70f9d55dd1078ac976431bd2b3246368 918878cbbe1e0a9a59058f6d81433751 a5a3de007da4558073bc00a2019ba5aa e2208039b64330e34aac9ec7020a063c ec89803672bb0d000f238009927343e7 SUSE LINUX 10.0: 89141c520781244c275ff2e2d8b4c1b5 968f25f3c344929b2f1754f4f9f5a0fc 8dcb79d36fda7785124038240bb40df0 50675e0b79610192a8f38fdaf4b655a3 d13657008290fc055958fac933b15beb 0829dd512ffe36216eba935288a37aff 71a78c27a97f620774c23b4a5ae9e1ac b4709e8c29aea15d130cd3df58e198f2 1b84a559b9c91895187707e08df7bb81 dbf8dc82c1b56af047402424fa36e889 52dc5bd08e8d0838a190d32abe6d9360 006f73bc4a0376aa6dcdb476773fac7f f4e37b49b4cd0cba088d1cbce4b6a106 d0d846db02bdfd31225fbceeb99a83d9 25e0ce59ffc1cc50eab7381029d9f37b 12c2317e35c03901605d35828ad97559 x86-64 Platform: SUSE LINUX 10.1: 2f9b1e124a86cd8d9434dc34ae704e34 eb35e4758f2367f14e63f93653d93929 e45fc3b3d4f6e6738e1be4a7756b3b87 022fcc53335d2521eef17fd2d9d5d65e 14aa868bfeeb53ccd484c542db37ca8f 3bc6667d6f053b9d737feee86548187a 0c5701fe6cb9689876d81edaa85376f1 c8c1f41f8dfd7053c20e831a4ef0dab9 ebd0e9c450d432e9d0330d535cf49e5f a13b9d5c42edcaf106fff4fa5518a25a e3906044737c10c7703908171adf3f57 f467c3939b354ed578f7157d8ef31ba7 d2f67c4278dff46c6467a5aa5d5ae21a 02e8931e0c337c91d7659ad6a6411f3e bc6f46f246e4a04db7ce73c4a9a8e14a 0c8256c4fb7cf7260871e260051e9cb8 44662d4d9dcbe2dcfdaed5aadf0d3280 3f1f16b27a5e82d4ec21813ff6d20de6 SUSE LINUX 10.0: faaafa4a6b2697b64002a0e54d966fb5 9bc2cc6f76d3ab0a3fa40e432ce8a5a5 b34db12ed5a82a0e421024924b8c9d35 9012ea42ee4342f5f33d0441d343dfbc 44a8e61f033f307894649a5f426a0201 8368c48caf6f752b5b95eb4eba3fd328 8ac64af18626a2a781ad07dd94c06d98 569cf2d488ceb8c75ce24509255db131 aa45bd963f675134c562cf337656a431 d27ef73513e09f0e13198ac917de4f5a a9a6390486569dd2a30404c2a1c720d1 952679113589f9568203b0f65e353be7 8e8477d1f0dbf6c58372655b94b2e763 b24ef527a716c2828bcbde7c64554f55 18b311d2694fec20cb8e91cace644b7a 58e7313cc4497968024c97bf9d0391e1 92ba868cfa14ec498100e5dd65ed907d SUSE LINUX 9.3: b0826412e85bbff760b5779fdc80ec94 98bd39be148e960ad27d8069c2adf8d1 156ae0023277a6160e87acc6ca8900d9 4fb514b18b529705623f7e6a0a215f19 db7ae6e63b7723c9f098c1e1ae8b4fd2 5b703b05cd53c20425ef68705c9373f8 a29f36a0cac395178ac22be57821862e 31a71ffbd976fb28c9d68d69faa8bcfd 241c1862886fd0a36afb17113a72858a b884e230f98ed60c5e75da726a498349 bd0a1137352eec2f3a8bc0d02f779a57 32f13ab54aafbd90ab70813c81bc4bb7 776af4929c99c7c5169baa9c9e114b91 d96f093d040a9f4b8d778a86a7b816e7 3e542aca65ef4dfbe9e395c3427f93c4 Sources: SUSE LINUX 10.1: 331cc1e61190283b14483c43a542b249 SUSE LINUX 10.0: 3d571d3a89e8b002b5adf330eb77fabc SUSE LINUX 9.3: bef98a4d3e3ecc2ce308b65b3614c701 Our maintenance customers are notified individually. The packages are offered for installation from the maintenance web: SUSE SLES 10 http://support.novell.com/techcenter/psdb/d0045f4fdf109a52c8482692f86759ac.html SLE SDK 10 http://support.novell.com/techcenter/psdb/d0045f4fdf109a52c8482692f86759ac.html SUSE SLED 10 http://support.novell.com/techcenter/psdb/d0045f4fdf109a52c8482692f86759ac.html SLES SDK 9 http://support.novell.com/techcenter/psdb/375ca96db35d471ce78d859b07e10e7a.html Novell Linux Desktop 9 http://support.novell.com/techcenter/psdb/375ca96db35d471ce78d859b07e10e7a.html Open Enterprise Server http://support.novell.com/techcenter/psdb/76c31e721b09466bd2ae950409714b5b.html ______________________________________________________________________________ 5) Pending Vulnerabilities, Solutions, and Work-Arounds: - dovecot off by one overflow Off-by-one buffer overflow in Dovecot 1.0 versions, when index files are used and mmap_disable is set to "yes," allows remote authenticated IMAP or POP3 users to cause a denial of service (crash) via unspecified vectors involving the cache file. (CVE-2006-5973) This update only affects SUSE Linux 10.1 and was released on November 27th. - xine-lib several overflows Multiple buffer overflows were fixed in the XINE decoder libraries, which could be used by attackers to crash players or potentially execute code. CVE-2006-4799: Buffer overflow in ffmpeg for xine-lib before 1.1.2 might allow context-dependent attackers to execute arbitrary code via a crafted AVI file and "bad indexes". CVE-2006-4800: Multiple buffer overflows in libavcodec in ffmpeg before 0.4.9_p20060530 allow remote attackers to cause a denial of service or possibly execute arbitrary code via multiple unspecified vectors in (1) dtsdec.c, (2) vorbis.c, (3) rm.c, (4) sierravmd.c, (5) smacker.c, (6) tta.c, (7) 4xm.c, (8) alac.c, (9) cook.c, (10) shorten.c, (11) smacker.c, (12) snow.c, and (13) tta.c. This update was released on 27th of November and affects all SUSE Linux based products containing xine-lib. - kdegraphics3 kfile_jpeg EXIF crashes The KFILE JPEG plugin that is responsible for displaying meta-data of JPEG files was affected by some old commonvulnerabilities in EXIF handling. A JPEG file could be prepared with an EXIF section with endless recursion that would overflow the stack and cause the plugin and so the image browser (konqueror, digikam or other kfile users) to crash. This problem can only be used for denial of service attacks. ______________________________________________________________________________ 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 inthis 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 This email address is being protected from spambots. You need JavaScript enabled to view it. 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 This email address is being protected from spambots. You need JavaScript enabled to view it.), 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: This email address is being protected from spambots. You need JavaScript enabled to view it. - General Linux and SUSE security discussion. All SUSE security announcements are sent to this list. To subscribe, send an e-mail to . This email address is being protected from spambots. You need JavaScript enabled to view it. - 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), sendmail to or . ==================================================================== SUSE's security contact is or . The public key is listed below. ==================================================================== . SUSE has issued a Security Advisory regarding the Mono core, which resolves issues related to local privilege escalation and potential code execution vulnerabilities.. Mono Security Update,SUSE Security Advisory,Local Privilege Escalation,Code Execution Risk. . Severity: Important. LinuxSecurity.com Team

Dec 01, 2006 •Important SuSE