# openSUSE-SU-2020:1016-1: Security update for mumble

> An attacker can exploit a potential vulnerability in the OCB2 encryption mode to compromise data confidentiality or integrity in Mumble.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Jul 2020

## What is openSUSE-SU-2020:1016-1?

openSUSE-SU-2020:1016-1 is a vulnerability in mumble, published on 20 Jul 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

This update for mumble fixes the following issues:

mumble was updated 1.3.2:

* client: Fixed overlay not starting

Update to upstream version 1.3.1

- Security
  * Fixed: Potential exploit in the OCB2 encryption (#4227)
    boo#1174041

- ICE

  * Fixed: Added missing UserKDFIterations field to UserInfo =>
    Prevents getRegistration() from failing with enumerator
    out of range error (#3835)

- GRPC

  * Fixed: Segmentation fault during murmur shutdown (#3938)

- Client

  * Fixed: Crash when using multiple monitors (#3756)
  * Fixed: Don't send empty message from clipboard via shortcut,
    if clipboard is empty (#3864)
  * Fixed: Talking indicator being able to freeze to indicate talking
    when self-muted (#4006)
  * Fixed: High CPU usage for update-check if update server not
    available (#4019)
  * Fixed: DBus getCurrentUrl returning empty string when not in
    root-channel (#4029)
  * Fixed: Small parts of whispering leaking out (#4051)
  * Fixed: Last audio frame of normal talking is sent to last
    whisper target (#4050)
  * Fixed: LAN-icon not found in ConnectDialog (#4058)
  * Improved: Set maximal vertical size for User Volume Adjustment
    dialog (#3801)
  * Improved: Don't send empty data to PulseAudio (#3316)
  * Improved: Use the SRV resolved port for UDP connections (#3820)
  * Improved: Manual Plugin UI (#3919)
  * Improved: Don't start Jack server by default (#3990)
  * Improved: Overlay doesn't hook into all other processes by
    default (#4041)
  * Improved: Wait longer before disconnecting from a server due
    to unanswered Ping-messages (#4123)

- Server

  * Fixed: Possibility to circumvent max user-count
    in channel (#3880)
  * Fixed: Rate-limit implementation susceptible to
    time-underflow (#4004)
  * Fixed: OpenSSL error 140E0197 with Qt >= 5.12.2 (#4032)
  * Fixed: VersionCheck for SQL for when to use the
    WAL feature (#4163)
  * Fixed: Wrong database encoding that could lead
    to server-crash (#4220)
  * Fixed: DB crash due to primary key violation
    (now performs 'UPSERT' to avoid this) (#4105)
  * Improved: The fields in the Version ProtoBuf message are
    now size-restricted (#4101)

- use the 'profile profilename /path/to/binary' syntax to make
  'ps aufxZ' more readable

## Which versions are affected by openSUSE-SU-2020:1016-1?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mumble` | openSUSE:Leap 15.1 | All versions | 1.3.2-lp152.2.3.1 |
| `mumble` | openSUSE:Leap 15.2 | All versions | 1.3.2-lp152.2.3.1 |

## How do I fix openSUSE-SU-2020:1016-1?

Upgrade to a fixed version.

## Is openSUSE-SU-2020:1016-1 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: openSUSE-SU-2020:1016-1 is a vulnerability in mumble, published on 20 Jul 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of openSUSE-SU-2020:1016-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-2020-1016-1/ (Markdown: https://insights.sbomify.com/openSUSE-SU-2020-1016-1/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/openSUSE-SU-2020:1016-1

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