dbcve.org
QuicktimeApplication · Apple

CVE-2013-1019

HIGH · 9.3 CVSS v2.0 Published 2013-05-24
Fix available
A fix is available. Upgrade to after 7.7.3 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Buffer overflow in Apple QuickTime before 7.7.4 allows remote attackers to execute arbitrary code or cause a denial of service (application crash) via a crafted movie file with Sorenson encoding.

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

Buffer overflow in Apple QuickTime before 7.7.4 when parsing crafted movie files with Sorenson encoding. The application fails to properly validate input size during video stream parsing, allowing memory corruption that can be leveraged for arbitrary code execution or denial of service.

MitigationUpgrade to QuickTime 7.7.4 or later to obtain vendor patch. Remove QuickTime if upgrade is not feasible and implement network-level controls to block QuickTime media files from untrusted 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
QuicktimeApplication
Affected:<= 7.7.3= 3.0= 4.1.2= 5.0= 5.0.1= 5.0.2= 6.0= 6.0.0= 6.0.1= 6.0.2= 6.1= 6.1.0
Iphone OsOperating system
Affected:<= 6.1.4= 1.0.0= 1.0.1= 1.0.2= 1.1.0= 1.1.1= 1.1.2= 1.1.3= 1.1.4= 1.1.5= 2.0= 2.0.0

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
M
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:M/Au:N/C:C/I:C/A:C

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 QuickTime installation
    Locate QuickTime on the system. On Windows, check Program Files/Common Files/Apple or the QuickTime folder in Program Files. On Mac, check /Applications for QuickTime Player.app.
    Affected if QuickTime is installed on the system
  2. Determine installed QuickTime version
    Open QuickTime and navigate to About QuickTime (Windows: Help > About QuickTime; Mac: QuickTime Player > About QuickTime Player) or right-click the QuickTime files to view Properties > Details.
    Affected if The reported version is 7.7.3 or earlier, or matches any of these affected versions: 3.0, 4.1.2, 5.0, 5.0.1, 5.0.2, 6.0, 6.0.0, 6.0.1, 6.0.2, 6.1, or 6.1.0
  3. Confirm QuickTime is actively used for media playback
    Check if QuickTime is set as the default handler for video files (.mov, .mp4, .avi) or if users routinely open video files using QuickTime Player.
    Affected if QuickTime is the default application for opening video files or is frequently used to play media files
  4. Check for iPhone OS devices
    If this detection is for an iPhone OS environment, verify the iOS version by going to Settings > General > About on the device.
    Affected if iPhone OS version is 6.1.4 or earlier, or matches any of these affected versions: 1.0.0, 1.0.1, 1.0.2, 1.1.0, 1.1.1, 1.1.2, 1.1.3, 1.1.4, 1.1.5, 2.0, or 2.0.0

You are affected if QuickTime version 7.7.3 or earlier is installed and used to play video files, or if an iPhone OS device runs version 6.1.4 or earlier, since the buffer overflow occurs when QuickTime parses crafted movie files with Sorenson encoding.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 7.7.3
Interim mitigation

Upgrade to QuickTime 7.7.4 or later to obtain vendor patch. Remove QuickTime if upgrade is not feasible and implement network-level controls to block QuickTime media files from untrusted sources.

Recommended fix High confidence

QuickTime 7.7.4

  1. 1. Open QuickTime Player on the system
  2. 2. Go to QuickTime Player menu > About QuickTime Player to check the current version
  3. 3. Navigate to Apple's official QuickTime download page or use Apple Software Update
  4. 4. Download QuickTime 7.7.4 or later
  5. 5. Close all QuickTime instances and any applications using QuickTime
  6. 6. Run the installer and follow the prompts to complete the installation
  7. 7. Verify the upgrade by checking About QuickTime Player again to confirm version 7.7.4 or higher is installed
Caveat QuickTime 7.7.4 is the final version for Windows; Apple discontinued QuickTime for Windows after this release - consider migrating to alternative media players if on Windows

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Quicktime Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing2.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,340
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-1019 — 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-2013-1019 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