pulseaudio socket needs confined app restrictions
Bug #1211380 reported by
Marc Deslauriers
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
PulseAudio |
New
|
Undecided
|
Unassigned | ||
apparmor (Ubuntu) |
Fix Released
|
Medium
|
Tyler Hicks | ||
Saucy |
Fix Released
|
Medium
|
Tyler Hicks | ||
Trusty |
Fix Released
|
Medium
|
Unassigned | ||
apparmor-easyprof-ubuntu (Ubuntu) |
Fix Released
|
Critical
|
Jamie Strandboge | ||
Saucy |
Fix Released
|
Critical
|
Jamie Strandboge | ||
Trusty |
Fix Released
|
Undecided
|
Unassigned | ||
pulseaudio (Ubuntu) |
Confirmed
|
Medium
|
Unassigned | ||
Saucy |
Won't Fix
|
Undecided
|
Unassigned | ||
Trusty |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
Confined applications need access to the pulseaudio socket. Currently several sockets are available to apps, and some allow performing dangerous operations, such as loading a module from an arbitrary path.
It also allows them to enumerate installed applications by listing clients.
The Pulseaudio daemon should verify if an application is confined, and if so, restrict access to certain commands.
If module loading cannot be disabled for confined applications, perhaps it could be modified to only load modules from trusted system locations.
Changed in pulseaudio (Ubuntu Saucy): | |
importance: | Undecided → Critical |
status: | New → Confirmed |
milestone: | none → ubuntu-13.10 |
Changed in pulseaudio (Ubuntu Saucy): | |
importance: | Critical → Undecided |
Changed in pulseaudio (Ubuntu): | |
importance: | Critical → Medium |
milestone: | ubuntu-13.10 → none |
description: | updated |
To post a comment you must log in.
Okay, how does PulseAudio determine if a client is confined or not?