dbcve.org
Mac Os XOperating system · Apple

CVE-2007-4677

HIGH · 9.3 CVSS v2.0 Published 2007-11-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
Heap-based buffer overflow in Apple QuickTime before 7.3 allows remote attackers to execute arbitrary code via an invalid color table size when parsing the color table atom (CTAB) in a movie file, related to the CTAB RGB values.

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 overflow in Apple QuickTime versions before 7.3 when parsing the color table atom (CTAB) in movie files. The vulnerability stems from insufficient validation of color table size fields, allowing an attacker to trigger an overflow via specially crafted CTAB RGB values and achieve arbitrary code execution.

MitigationUpdate QuickTime to version 7.3 or later to patch the vulnerability. Until patched, avoid opening movie files from untrusted sources, as the flaw can be triggered via malicious QuickTime movie files.

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
Mac Os XOperating system
Affected:= 10.3.9= 10.4.10= 10.5
Windows VistaOperating system
Affected:all versions
Windows XpOperating system
Affected:all versions

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. Check if QuickTime is installed
    On Windows, check for C:\Program Files\QuickTime\QuickTime.exe or C:\Program Files (x86)\QuickTime\QuickTime.exe. On Mac OS X, check for /Applications/QuickTime Player.app
    Affected if QuickTime executable is present on the system
  2. Determine installed QuickTime version
    On Windows, right-click QuickTime.exe, select Properties, and view the Version tab. On Mac OS X, right-click QuickTime Player.app, select Get Info, and view the Version field
    Affected if Unable to determine the installed version
  3. Compare version to vulnerable range
    Compare the installed QuickTime version number to the affected range (versions before 7.3)
    Affected if Installed version is 7.2 or earlier, or any version less than 7.3
  4. Check if CTAB parsing is reachable
    This vulnerability is triggered when QuickTime parses a specially crafted movie file containing a malicious color table atom (CTAB)
    Affected if User opens a crafted QuickTime movie file with a malformed CTAB atom

The system is affected if QuickTime version 7.2 or earlier is installed and the user opens a malicious QuickTime movie file containing a specially crafted CTAB color table.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update QuickTime to version 7.3 or later to patch the vulnerability. Until patched, avoid opening movie files from untrusted sources, as the flaw can be triggered via malicious QuickTime movie files.

Recommended fix High confidence

QuickTime 7.3 or later

  1. Open QuickTime Player and go to QuickTime Player > About QuickTime Player to check the current version number
  2. Navigate to Apple's QuickTime download page or use Apple Software Update to check for available updates
  3. Download QuickTime 7.3 or later (the latest available version is recommended)
  4. Close all applications using QuickTime
  5. Install the QuickTime update following the installation wizard prompts
  6. Restart the computer if prompted
  7. Verify the installation by checking About QuickTime Player to confirm version 7.3 or higher is installed
Caveat QuickTime 7.3 was a significant update that may have changed some encoding defaults or codec support; test critical media workflows after upgrading

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

Fix this in Mac Os X Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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