Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 16 Feb 2012 15:35:55 +0100
From: Ludwig Nussel <>
	Vincent Untz <>
Subject: Re: CVE request: mumble local information disclosure

Vincent Danen wrote:
> It was discovered that mumble created its database file
> (~/.local/share/data/Mumble/.mumble.sqlite) with insecure world-readable
> permissions.  If the user had (non-default) permissions on their home
> directory, another local user could obtain password and configuration
> settings from the database file.

It certainly makes sense for cautios applications to make sure sensitive
settings have restricted access permissions. Question is whether it is
actually a vulnerability if they don't. Quoting the XDG spec¹

| If, when attempting to write a file, the destination directory is
| non-existant an attempt should be made to create it with permission
| 0700. If the destination directory exists already the permissions should
| not be changed.

So it could be argued that mumble just relied on the specification that
already mandates restrictive permissions on ~/.config.

The program that is supposed to create ~/.config on login had a bug that
made the dir 755 in violation of the spec². Fixing the permissions is
not allowed according to the spec though ...



 (o_   Ludwig Nussel
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) 

Powered by blists - more mailing lists

Please check out the Open Source Software Security Wiki, which is counterpart to this mailing list.

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.