Bug 570701 (CVE-2009-1299) - CVE-2009-1299 pulseaudio: information disclosure or DoS due to temporary directory handling
Summary: CVE-2009-1299 pulseaudio: information disclosure or DoS due to temporary dire...
Alias: CVE-2009-1299
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL: http://web.nvd.nist.gov/view/vuln/det...
Depends On: 571815
TreeView+ depends on / blocked
Reported: 2010-03-05 03:07 UTC by Vincent Danen
Modified: 2019-09-29 12:35 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2011-09-09 08:28:49 UTC

Attachments (Terms of Use)

Description Vincent Danen 2010-03-05 03:07:03 UTC
Dan Rosenberg reported a vulnerability in pulseaudio's handling of temporary directories, which can be used by an attacker to create a Denial of Service condition or possibly disclose sensitive information to unprivileged users.

When pulseaudio starts, it creates a temporary directory with a predictable name (/tmp/.esd-[uid], where [uid] is the user id of the user executing the pulseaudio process).  If the directory already exists, pulseaudio does not create a new one; it also does not check for symbolic links.  After the directory is created, or if it already exists, pulseaudio will chown the directory to the uid/gid of the user running pulseaudio, and then chmods it to either 0700 or 0755 (the latter if it is running in 'system mode').  Depending on whether an attacker can create an appropriate symbolic link, this could result in linked files being given inappropriate permissions depending on the user executing pulseaudio, and whether it is in 'system mode' or not, which could possibly lead to information disclosure or a DoS if files/executables requiring one set of permissions are given another set that a particular program may refuse to run with (for example, .fetchmailrc or ssh configuration files).

The upstream commit fixing this issue is available here:


Comment 2 Vincent Danen 2010-03-09 15:42:32 UTC
Embargo lifted as the Ubuntu bug is now public:


Note You need to log in before you can comment on or make changes to this bug.