# CVE-2009-0397: Memory corruption in n/a

> Remote attackers can execute arbitrary code via crafted QuickTime files due to a heap-based buffer overflow in GStreamer plugins.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **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:** 3 Feb 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-68wh-jxh5-cwrj, PYSEC-2009-16, RHSA-2009:0270

## What is CVE-2009-0397?

CVE-2009-0397 is a critical memory corruption vulnerability in n/a, published on 3 Feb 2009. 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

Heap-based buffer overflow in the qtdemux_parse_samples function in gst/qtdemux/qtdemux.c in GStreamer Good Plug-ins (aka gst-plugins-good) 0.10.9 through 0.10.11, and GStreamer Plug-ins (aka gstreamer-plugins) 0.8.5, might allow remote attackers to execute arbitrary code via crafted Time-to-sample (aka stts) atom data in a malformed QuickTime media .mov file.

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

## Which versions are affected by CVE-2009-0397?

1 open source package ship an affected version, including gstreamer-plugins. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gstreamer-plugins` | PyPI | All versions to 0.10.9 | None |
| `gstreamer-plugins` | Red Hat:enterprise_linux:4::as | All versions | 0:0.8.5-1.EL.2 |
| `gstreamer-plugins-debuginfo` | Red Hat:enterprise_linux:4::as | All versions | 0:0.8.5-1.EL.2 |
| `gstreamer-plugins-devel` | Red Hat:enterprise_linux:4::as | All versions | 0:0.8.5-1.EL.2 |
| `gstreamer-plugins` | Red Hat:enterprise_linux:4::desktop | All versions | 0:0.8.5-1.EL.2 |
| `gstreamer-plugins-debuginfo` | Red Hat:enterprise_linux:4::desktop | All versions | 0:0.8.5-1.EL.2 |
| `gstreamer-plugins-devel` | Red Hat:enterprise_linux:4::desktop | All versions | 0:0.8.5-1.EL.2 |
| `gstreamer-plugins` | Red Hat:enterprise_linux:4::es | All versions | 0:0.8.5-1.EL.2 |
| `gstreamer-plugins-debuginfo` | Red Hat:enterprise_linux:4::es | All versions | 0:0.8.5-1.EL.2 |
| `gstreamer-plugins-devel` | Red Hat:enterprise_linux:4::es | All versions | 0:0.8.5-1.EL.2 |
| `gstreamer-plugins` | Red Hat:enterprise_linux:4::ws | All versions | 0:0.8.5-1.EL.2 |
| `gstreamer-plugins-debuginfo` | Red Hat:enterprise_linux:4::ws | All versions | 0:0.8.5-1.EL.2 |
| `gstreamer-plugins-devel` | Red Hat:enterprise_linux:4::ws | All versions | 0:0.8.5-1.EL.2 |

Products: Gstreamer Good Plug-Ins, Gstreamer Plug-Ins.

## How do I fix CVE-2009-0397?

Upgrade to a fixed version.

## Is CVE-2009-0397 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-0386](https://insights.sbomify.com/CVE-2009-0386/): Memory corruption in n/a (critical 9.3)
- [CVE-2009-0387](https://insights.sbomify.com/CVE-2009-0387/): Memory corruption in n/a (critical 9.3)
- [CVE-2009-1932](https://insights.sbomify.com/CVE-2009-1932/): Integer overflow in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-0397 and fix it if it is affected.

What it is: CVE-2009-0397 is a critical memory corruption vulnerability in n/a, published on 3 Feb 2009. 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-2009-0397 in the wild and no public exploit code.

Affected packages and fixed versions:
- gstreamer-plugins (PyPI): affected all versions up to 0.10.9; no fix listed

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-2009-0397/ (Markdown: https://insights.sbomify.com/CVE-2009-0397/index.md)
```

## Sources

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

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