Mumble before 1.3.4 allows remote code execution if a victim navigates to a crafted URL on a server list and clicks on the Open Webpage text.

murmur in Mumble through 1.2.19 before 2018-08-31 mishandles multiple concurrent requests that are persisted in the database, which allows remote attackers to cause a denial of service (daemon hang or crash) via a message flood.

Qt 5.12.2 through 5.14.2, as used in unofficial builds of Mumble 1.3.0 and other products, mishandles OpenSSL's error queue, which can cause a denial of service to QSslSocket users. Because errors leak in unrelated TLS sessions, an unrelated session may be disconnected when any handshake fails. (Mumble 1.3.1 is not affected, regardless of the Qt version.)

Mumble: murmur-server has DoS due to malformed client query

Mumble before 1.6.870 is prone to an out-of-bounds array access, which may result in denial of service (client crash).

The QSvg module in Qt, as used in the Mumble client 1.2.x before 1.2.6, allows remote attackers to cause a denial of service (hang and resource consumption) via a local file reference in an (1) image tag or (2) XML stylesheet in an SVG file.

The client in Mumble 1.2.x before 1.2.6 allows remote attackers to force the loading of an external file and cause a denial of service (hang and resource consumption) via a crafted string that is treated as rich-text by a Qt widget, as demonstrated by the (1) user or (2) channel name in a Qt dialog, (3) subject common name or (4) email address to the Certificate Wizard, or (5) server name in a tooltip.

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

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