On this page (7 sections)
Ubuntu has published security notice USN-9143-1 for Mumble. The notice says the Murmur server component did not rate limit certain client messages, so a remote attacker could possibly make Murmur hang or crash, resulting in a denial of service.
If you host a Mumble (Murmur) voice chat server for a community, a game group, a team or a client, this is the notice to read. The impact the notice describes is loss of availability: a hang or crash of the server.
What happened
According to the Ubuntu notice, the Murmur server did not rate limit certain client messages. An attacker able to reach the server could possibly abuse that to make the process hang or crash. The notice words this cautiously ("could possibly"), so treat it as a realistic availability risk rather than a confirmed, widely exploited attack.
The vendor's remedy is not only a bug fix but a new control: the updated package adds a message rate limit that an administrator can tune with two settings, messageburst and messagelimit.
The weakness in plain terms
Missing rate limiting is a common cause of denial of service. A server that handles every incoming message at full cost, no matter how many arrive, can be pushed into using too much CPU, memory or processing time. If a client can send a particular kind of message repeatedly and quickly, the server may stall (hang) or terminate (crash), and every connected user loses the service.
A rate limit works as a speed bump. It lets normal bursts through but caps sustained traffic from a single client. The two setting names in the notice suggest this design: one relating to bursts, the other to a limit. The notice does not document their exact semantics or default values, so check the Mumble documentation or the shipped configuration file before changing them.
Who is exposed
- Administrators who run Murmur on Ubuntu from the distribution's Mumble packages and have not yet applied the update.
- Servers reachable from the internet, since the notice describes a remote attacker.
- Public or semi-public servers where anyone can connect as a client. Whether authentication is required before the affected messages are accepted is not stated in the notice, so do not assume a password protects you.
- Communities that depend on the server for live voice, where a crash or hang is immediately noticeable.
If you only use the Mumble desktop client to join other people's servers, the notice concerns the server component. Your server operator is the one who needs to update.
How to check your exposure
First find out whether Murmur is installed and running on the host. The following read-only commands work on Ubuntu and Debian-based systems. The first lists installed packages with mumble in the name and their versions; the second shows whether a Murmur process is running.
dpkg -l | grep -i mumbleps aux | grep -i [m]urmurCompare the installed package version with the fixed version listed for your Ubuntu release in the notice. If your version is older than the fixed one, you need to update.
Also confirm who can reach the service. Murmur listens on a network port for voice clients, so check your firewall or cloud security group rules to see whether it is open to the whole internet or only to the networks that need it.
What to do now
- Read USN-9143-1 and note the fixed package version for your Ubuntu release.
- Refresh package lists and upgrade the installed Mumble server package (commands below).
- Restart Murmur if the upgrade did not do it, then confirm the service is running.
- Review the messageburst and messagelimit settings in your Murmur configuration and keep them reasonable for your normal usage.
- Restrict network access to the server port to the networks that need it, where that is practical.
- Watch the service for crashes or hangs over the next days and set up an alert for downtime.
On Ubuntu, refresh the package index and upgrade only the Mumble server package if it is already installed. The package name below is the one commonly used on Debian and Ubuntu.
sudo apt update
sudo apt install --only-upgrade mumble-serverAfterward, show the installed and candidate versions so you can compare them with the notice.
apt-cache policy mumble-serverDetection and monitoring
A denial of service against a voice server shows up as users being dropped, the service not answering, or the process disappearing. Practical signals to watch:
- Unexpected restarts or exits of the Murmur process, visible in the system journal or service manager status.
- Sudden spikes in CPU use by the Murmur process, or a process that is running but not responding to clients.
- A single remote address generating unusually high message volume in your network logs.
- Repeated reports from users that they cannot connect or keep getting kicked.
Basic uptime checks on the server port catch an outage quickly. Webforta Monitor covers uptime, certificate and DNS monitoring, and our guide to uptime monitoring explains how to choose check intervals. Monitoring tells you something is wrong; it does not stop an attack or patch the software.
For broader background on traffic floods aimed at small services, see our overview of DDoS protection basics. Rate limiting inside the application, as this update adds, is a different layer from network-level protection, and the two complement each other.
What is still unknown
The research behind this article is a single vendor notice, and only one publisher covers the story so far. The notice does not say whether the issue is being exploited, who found it, what severity score it carries, or whether a CVE exists. It also does not describe which client messages are affected. If any of those details are published later, they will matter for prioritizing, but the vendor fix is available now and the safe course is to apply it.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
