REDHAT-BUG-791000: SQL Injection

Published Feb 15, 2012
·
Updated

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 [1].

This has been corrected in upstream git [2] and is reported as affecting 1.2.3 and earlier.

[1] https://bugs.launchpad.net/ubuntu/+source/mumble/+bug/783405 [2] https://github.com/mumble-voip/mumble/commit/5632c35d6759f5e13a7dfe78e4ee6403ff6a8e3e

Affected Software

1 affected component
Mumble Mumble<1.2.3

Event History

Feb 15, 2012
Data Sourced
via Red Hat·10:06 PM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the severity of REDHAT-BUG-791000?

The severity of REDHAT-BUG-791000 is considered high due to the exposure of sensitive information.

2

How do I fix REDHAT-BUG-791000?

To fix REDHAT-BUG-791000, ensure that the database file permissions are set correctly to restrict access to only the owner.

3

Which versions of Mumble are affected by REDHAT-BUG-791000?

Mumble versions earlier than 1.2.4 are affected by REDHAT-BUG-791000.

4

What potential risks are associated with REDHAT-BUG-791000?

The main risk associated with REDHAT-BUG-791000 is that unauthorized users can access stored passwords and configuration settings.

5

Who is responsible for addressing REDHAT-BUG-791000?

The Mumble development team is responsible for addressing REDHAT-BUG-791000, and users should apply the software updates as released.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203