# CVE-2014-0044: Null dereference in n/a

> Remote attackers can crash the Mumble VoIP client by sending a crafted packet, causing a denial of service via null pointer dereference or buffer over-read.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Feb 2014
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2014-0044, GHSA-649v-fxxp-vqjg

## What is CVE-2014-0044?

CVE-2014-0044 is a medium-severity vulnerability in n/a, published on 8 Feb 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The opus_packet_get_samples_per_frame function in client in Mumble 1.2.4 and the 1.2.3 pre-release snapshots allows remote attackers to cause a denial of service (crash) via a crafted length prefix value, which triggers a NULL pointer dereference or a heap-based buffer over-read (aka "out-of-bounds array access").

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2014-0044?

It affects 1 product.


Products: Light Speed Gaming Mumble.

## How do I fix CVE-2014-0044?

Upgrade to a fixed version.

## Is CVE-2014-0044 being exploited?

There is no known exploitation of CVE-2014-0044 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2014-0045](https://insights.sbomify.com/CVE-2014-0045/): Integer overflow in n/a (high 7.5)
- [CVE-2014-1916](https://insights.sbomify.com/CVE-2014-1916/): Null dereference in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-0044 and fix it if it is affected.

What it is: CVE-2014-0044 is a medium-severity vulnerability in n/a, published on 8 Feb 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-0044 in the wild and no public exploit code.

Affected product: n/a. 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/CVE-2014-0044/ (Markdown: https://insights.sbomify.com/CVE-2014-0044/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2014-0044
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2014-0044
- OSV: https://osv.dev/vulnerability/CVE-2014-0044

---
From sbomify Insights: https://insights.sbomify.com/CVE-2014-0044/
Summaries are generated and may contain mistakes; the official description above is the record.