# CVE-2015-0797: Memory corruption in n/a

> Remote attackers can cause denial of service or execute arbitrary code via crafted H.264 video data in GStreamer, affecting Firefox and Thunderbird users.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **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:** 14 May 2015
- **Updated:** 6 Aug 2024
- **Also known as:** DSA-3225-1, GHSA-wvj4-9m85-jjv9, MGASA-2015-0188, SUSE-SU-2015:0921-1, SUSE-SU-2015:0942-1, UBUNTU-CVE-2015-0797, openSUSE-SU-2024:10429-1

## What is CVE-2015-0797?

CVE-2015-0797 is a medium-severity memory corruption vulnerability in Debian Debian Linux, published on 14 May 2015. 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

GStreamer before 1.4.5, as used in Mozilla Firefox before 38.0, Firefox ESR 31.x before 31.7, and Thunderbird before 31.7 on Linux, allows remote attackers to cause a denial of service (buffer over-read and application crash) or possibly execute arbitrary code via crafted H.264 video data in an m4v file.

## Which versions are affected by CVE-2015-0797?

It affects 14 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gstreamer-0_10-plugins-bad` | SUSE:Linux Enterprise Desktop 12 | All versions | 0.10.23-17.1 |
| `gstreamer-0_10-plugins-bad` | SUSE:Linux Enterprise Software Development Kit 12 | All versions | 0.10.23-17.1 |
| `gstreamer-0_10-plugins-bad` | SUSE:Linux Enterprise Workstation Extension 12 | All versions | 0.10.23-17.1 |

Products: Debian Debian Linux, Gstreamer Gstreamer, Mozilla Firefox, Mozilla Seamonkey, Mozilla Thunderbird, Redhat Enterprise Linux Desktop, Redhat Enterprise Linux Eus, Redhat Enterprise Linux Server, Redhat Enterprise Linux Server Aus, Redhat Enterprise Linux Server Tus, Redhat Enterprise Linux Workstation, Suse Linux Enterprise Desktop, Suse Linux Enterprise Server, Suse Linux Enterprise Software Development Kit.

## How do I fix CVE-2015-0797?

Upgrade to a fixed version.

## Is CVE-2015-0797 being exploited?

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

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-0797 and fix it if it is affected.

What it is: CVE-2015-0797 is a medium-severity memory corruption vulnerability in Debian Debian Linux, published on 14 May 2015. 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 CVE-2015-0797 in the wild and no public exploit code.

Affected product: Debian Debian Linux. 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-2015-0797/ (Markdown: https://insights.sbomify.com/CVE-2015-0797/index.md)
```

## Sources

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

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