dbcve.org
ItunesApplication · Apple

CVE-2005-4092

HIGH · 7.5 CVSS v2.0 Published 2005-12-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Multiple heap-based buffer overflows in QuickTime.qts in Apple QuickTime Player 7.0.3 and iTunes 6.0.1 (3) and earlier allow remote attackers to cause a denial of service (crash) and execute arbitrary code via a .mov file with (1) a Movie Resource atom with a large size value, or (2) an stsd atom with a modified Sample Description Table size value, and possibly other vectors involving media files. NOTE: item 1 was originally identified by CVE-2005-4127 for a pre-patch announcement, and item 2 was originally identified by CVE-2005-4128 for a pre-patch announcement.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Heap-based buffer overflows in QuickTime.qts when parsing specially crafted .mov files containing malformed Movie Resource atoms with large size values or stsd atoms with modified Sample Description Table size values. Successful exploitation allows denial of service or arbitrary code execution.

MitigationUpdate affected QuickTime Player to version 7.0.4 or later and iTunes to version 6.0.2 or later. Avoid opening untrusted .mov files from unknown sources.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ItunesApplication
Affected:= 6.0.1
QuicktimeApplication
Affected:= 7.0.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:N/C:P/I:P/A:P

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed QuickTime Player version
    On Windows, open Control Panel > Programs and Features or right-click QuickTime in system tray and select 'About QuickTime Player'. On Mac, open Finder > Applications and right-click QuickTime Player > Get Info. Note the version number displayed.
    Affected if Version is exactly 7.0.3 (the only affected QuickTime version listed)
  2. Identify installed iTunes version
    On Windows, open Control Panel > Programs and Features or open iTunes and go to Help > About iTunes. On Mac, open iTunes and go to iTunes > About iTunes. Note the version number displayed.
    Affected if Version is exactly 6.0.1 (the only affected iTunes version listed)
  3. Verify QuickTime system component presence
    On Windows, check for QuickTime.qts file in the QuickTime system folder (typically C:\Windows\System32\QuickTime or C:\Program Files\QuickTime\QTSystem). On Mac, check /Library/QuickTime/QuickTime.qts exists.
    Affected if QuickTime.qts exists and is being used by the affected QuickTime or iTunes versions identified above
  4. Confirm active file parsing exposure
    Check if QuickTime is configured as a handler for .mov files in the system or if any applications register QuickTime for media decoding. On Windows, check Default Programs > Set Associations. On Mac, check Finder > Get Info for .mov files.
    Affected if QuickTime or iTunes is set as the default handler for .mov files and the affected versions (7.0.3 or 6.0.1) are installed

You are affected if QuickTime Player 7.0.3 or iTunes 6.0.1 is installed and configured to handle .mov files, as the vulnerability lies in the QuickTime.qts component parsing malformed Movie Resource or stsd atoms within those files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update affected QuickTime Player to version 7.0.4 or later and iTunes to version 6.0.2 or later. Avoid opening untrusted .mov files from unknown sources.

Fix this in Itunes Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2005-4092 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2005-4092 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data