# CVE-2011-3428: Buffer overflow in QuickTime before 7.7.1 for Windows allows remote attackers to execute arbitrary code.


- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 24 Apr 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-q3xw-qwr2-8r9r

## What is CVE-2011-3428?

CVE-2011-3428 is a critical vulnerability in Apple Quicktime, published on 24 Apr 2017. 

### Official description

Buffer overflow in QuickTime before 7.7.1 for Windows allows remote attackers to execute arbitrary code.

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

## Which versions are affected by CVE-2011-3428?

It affects 1 product.


Products: Apple Quicktime.

## How do I fix CVE-2011-3428?

No fix has been published for CVE-2011-3428 yet. Limit exposure of the affected software until one is available.

## Is CVE-2011-3428 being exploited?

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

## Other vulnerabilities in Apple Quicktime

- [CVE-2007-6238](https://insights.sbomify.com/CVE-2007-6238/): Other in n/a (critical 10.0)
- [CVE-2014-4979](https://insights.sbomify.com/CVE-2014-4979/): Memory corruption in n/a (critical 9.3)
- [CVE-2014-1243](https://insights.sbomify.com/CVE-2014-1243/): Memory corruption in n/a (critical 9.3)
- [CVE-2014-1244](https://insights.sbomify.com/CVE-2014-1244/): Memory corruption in n/a (critical 9.3)
- [CVE-2014-1245](https://insights.sbomify.com/CVE-2014-1245/): Integer overflow in n/a (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-3428 and fix it if it is affected.

What it is: CVE-2011-3428 is a critical vulnerability in Apple Quicktime, published on 24 Apr 2017. 
Exploitation: There is no known exploitation of CVE-2011-3428 in the wild and no public exploit code.

Affected product: Apple Quicktime. 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-2011-3428/ (Markdown: https://insights.sbomify.com/CVE-2011-3428/index.md)
```

## Sources

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

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