# openSUSE-SU-2021:0312-1: Security update for mumble

> An attacker can exploit non-http/https URL schemes in the public server list to potentially execute code, requiring user interaction.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 19 Feb 2021

## What is openSUSE-SU-2021:0312-1?

openSUSE-SU-2021:0312-1 is a vulnerability in mumble, published on 19 Feb 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

This update for mumble fixes the following issues:

mumble was updated to 1.3.4:

* Fix use of outdated (non-existent) notification icon names
* Fix Security vulnerability caused by allowing non http/https
  URL schemes in public server list (boo#1182123)
* Server: Fix Exit status for actions like --version or --supw
* Fix packet loss & audio artifacts caused by OCB2 XEX*
  mitigation

- update apparmor profiles to get warning free again on 15.2
  - use abstractions for ssl files
  - allow inet dgram sockets as mumble can also work via udp
  - allow netlink socket (probably for dbus)
  - properly allow lsb_release again
  - add support for optional local include
- start murmurd directly as user mumble-server it gets rid of the
  dac_override/setgid/setuid/chown permissions

Update to upstream version 1.3.3

Client:

* Fixed: Chatbox invisble (zero height) (#4388)
* Fixed: Handling of invalid packet sizes (#4394)
* Fixed: Race-condition leading to loss of shortcuts (#4430)
* Fixed: Link in About dialog is now clickable again (#4454)
* Fixed: Sizing issues in ACL-Editor (#4455)
* Improved: PulseAudio now always samples at 48 kHz (#4449)

Server:

* Fixed: Crash due to problems when using PostgreSQL (#4370)
* Fixed: Handling of invalid package sizes (#4392)

This update was imported from the openSUSE:Leap:15.2:Update update project.

## Which versions are affected by openSUSE-SU-2021:0312-1?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mumble` | SUSE:Package Hub 15 SP2 | All versions | 1.3.4-bp152.2.6.1 |

## How do I fix openSUSE-SU-2021:0312-1?

Upgrade to a fixed version.

## Is openSUSE-SU-2021:0312-1 being exploited?

There is no known exploitation of openSUSE-SU-2021:0312-1 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for openSUSE-SU-2021:0312-1 and fix it if it is affected.

What it is: openSUSE-SU-2021:0312-1 is a vulnerability in mumble, published on 19 Feb 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of openSUSE-SU-2021:0312-1 in the wild and no public exploit code.

Affected product: mumble. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/openSUSE-SU-2021-0312-1/ (Markdown: https://insights.sbomify.com/openSUSE-SU-2021-0312-1/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/openSUSE-SU-2021:0312-1

---
From sbomify Insights: https://insights.sbomify.com/openSUSE-SU-2021-0312-1/
Summaries are generated and may contain mistakes; the official description above is the record.