1.2.13

From Mumble Wiki
Jump to: navigation, search
Release timeline
1.2.0
Dec. 2009
1.2.1
Jan. 2010
1.2.2
Feb. 2010
1.2.3
Feb. 2011
1.2.4
Jun. 2013
1.2.5
Feb. 2014
1.2.6
May 2014
1.2.7
Jun. 2014
1.2.8
Aug. 2014
1.2.9
Jun. 2015
1.2.10
Jul. 2015
1.2.11
Dec. 2015
1.2.12
Dec. 2015
1.2.13
Jan. 2016
1.2.14
Feb. 2016
1.2.15
Mar. 2016
1.2.16
May. 2016
1.2.17
Sep. 2016
1.3.0
in development
Future


Mumble 1.2.13 fixes a security-relevant bug in Murmur when running on Windows systems that allowed an unauthenticated user to cause Denial of Service on the server’s UDP connection.

We would like to thank LuaMilkshake for responsibly reporting this issue to the Mumble project.

This release of Mumble on Windows is also the first stable release in the 1.2-series that is only code-signed with a SHA256 authenticode signature and certificate. Previous releases were signed by both a SHA1 signature and certificate, as well as a SHA256 signature and certificate.

This new code-signing setup can cause issues with some versions of Windows that do not support SHA256 code-signing. If your Mumble installer on Windows does not seem to be Authenticode signed, it probably means that your version of Windows does not support SHA256 code-signing. In that case, we recommend that you ensure the integrity of your Mumble installer by verifying the detached GPG signature (mumble-1.2.13.msi.sig) against our "Mumble Automatic Build Infrastructure 2016" GPG key.

Issues fixed in this release include:

In previous versions of Mumble, it was possible to perform a Denial of Service attack on Murmur servers running on Windows. See Mumble-SA-2016-001 (sig) for more information.

For a full changelog, please see the diff between 1.2.12 and 1.2.13 on GitHub.

We recommend that all users of Murmur (the server component of Mumble) on Windows upgrade immediately.