[ advisories | exploits | discussions | news | conventions | security tools | texts & papers ]
 main menu
- feedback
- advertising
- privacy
- FightAIDS
- newsletter
- news
 
 discussions
- read forum
- new topic
- search
 

 meetings
- meetings list
- recent additions
- add your info
 
 top 100 sites
- visit top sites
- sign up now
- members
 
 webmasters

- add your url
- add domain
- search box
- link to us

 
 projects
- our projects
- free email
 
 m4d network
- security software
- secureroot
- m4d.com
Home : Advisories : esound contains a race condition

Title: esound contains a race condition
Released by: Red Hat
Date: 6th October 2000
Printable version: Click here
---------------------------------------------------------------------

                   Red Hat, Inc. Security Advisory



Synopsis:          esound contains a race condition

Advisory ID:       RHSA-2000:077-03

Issue date:        2000-10-06

Updated on:        2000-10-06

Product:           Red Hat Linux

Keywords:          esound security esd socket Gnome

Cross references:  N/A

---------------------------------------------------------------------



1. Topic:



Esound, the Gnome sound server, contains a race condition that a malicious

user could exploit to change permissions of any file owned by the esound

user.



2. Relevant releases/architectures:



Red Hat Linux 6.0 - i386, alpha, sparc

Red Hat Linux 6.1 - i386, alpha, sparc

Red Hat Linux 6.2 - i386, alpha, sparc

Red Hat Linux 6.2EE - i386, alpha, sparc

Red Hat Linux 7.0 - i386

Red Hat Linux 7.0J - i386



3. Problem description:



Esound, the sound daemon used for Gnome, creates a world-writable

directory, /tmp/.esd.  This directory is owned by the user running esound,

and is used to store a socket which is used by programs connecting to the

sound server.  During startup, this socket's permissions are adjusted. An

attacker on the system can theoretically create a symbolic link, and cause

any file or directory owned by the user running esound to be made

world writable.



The new packages fixes this race condition.



4. Solution:



For each RPM for your particular architecture, run:



rpm -Fvh [filename]



where filename is the name of the RPM.



All active Gnome sessions should also be restarted after the upgrade is

applied.



5. Bug IDs fixed (http://bugzilla.redhat.com/bugzilla for more info):



N/A



6. RPMs required:



Red Hat Linux 6.x:



alpha:

http://updates.redhat.com/6.2/alpha/esound-0.2.20-0.alpha.rpm

http://updates.redhat.com/6.2/alpha/esound-devel-0.2.20-0.alpha.rpm



sparc:

http://updates.redhat.com/6.2/sparc/esound-0.2.20-0.sparc.rpm

http://updates.redhat.com/6.2/sparc/esound-devel-0.2.20-0.sparc.rpm



i386:

http://updates.redhat.com/6.2/i386/esound-0.2.20-0.i386.rpm

http://updates.redhat.com/6.2/i386/esound-devel-0.2.20-0.i386.rpm



sources:

http://updates.redhat.com/6.2/SRPMS/esound-0.2.20-0.src.rpm



Red Hat Linux 7.0:



i386:

http://updates.redhat.com/7.0/i386/esound-0.2.20-1.i386.rpm

http://updates.redhat.com/7.0/i386/esound-devel-0.2.20-1.i386.rpm



sources:

http://updates.redhat.com/7.0/SRPMS/esound-0.2.20-1.src.rpm



7. Verification:



MD5 sum                           Package Name

--------------------------------------------------------------------------

4f7a81fe6b7f5a419272659b92d1dfc1  6.2/SRPMS/esound-0.2.20-0.src.rpm

648746086daa7bbc6bef00697e62bf51  6.2/alpha/esound-0.2.20-0.alpha.rpm

8a7dbf7dabbd7d9ca2861c1ecf2b2d5f  6.2/alpha/esound-devel-0.2.20-0.alpha.rpm

962fa1129804f2d8470e1767a352f77f  6.2/i386/esound-0.2.20-0.i386.rpm

784ec77026228d31d823e619c1de78d8  6.2/i386/esound-devel-0.2.20-0.i386.rpm

2127fdd7654b80506952dce08c3f5014  6.2/sparc/esound-0.2.20-0.sparc.rpm

0c191eee05a89dc0d12b3ca4981d2353  6.2/sparc/esound-devel-0.2.20-0.sparc.rpm

24f8e1b106500565e8426ad96150a001  7.0/SRPMS/esound-0.2.20-1.src.rpm

a61209acb87ed7f4fa5b1d63d161c85d  7.0/i386/esound-0.2.20-1.i386.rpm

6b326c66d570ee59eda7c2daf0ab4721  7.0/i386/esound-devel-0.2.20-1.i386.rpm



These packages are GPG signed by Red Hat, Inc. for security.  Our key

is available at:

    http://www.redhat.com/corp/contact.html



You can verify each package with the following command:

    rpm --checksig  



If you only wish to verify that each package has not been corrupted or

tampered with, examine only the md5sum with the following command:

    rpm --checksig --nogpg 



8. References:



BugTraq ID: 1659 (http://www.securityfocus.com/bid/1659)





Copyright(c) 2000 Red Hat, Inc.








(C) 1999-2000 All rights reserved.