dbcve.org
Mac Os XOperating system · Apple

CVE-2007-4676

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 malformed elements when parsing (1) Poly type (0x0070 through 0x0074) and (2) PackBitsRgn field (0x0099) opcodes in a PICT image.

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 prior to 7.3 when parsing malformed PICT image files. The vulnerability is triggered by specially crafted Poly type opcodes (0x0070-0x0074) and PackBitsRgn field opcode (0x0099), allowing remote attackers to execute arbitrary code via heap corruption.

MitigationUpdate Apple QuickTime to version 7.3 or later. Until updated, avoid opening untrusted or unknown PICT image 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
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. Verify QuickTime is installed
    On Windows: Check for QuickTime in Add/Remove Programs or look for QuickTime Player in Program Files. On Mac: Check /Applications folder for QuickTime Player or run 'ls /Applications | grep -i quicktime'
    Affected if QuickTime is not installed on the system
  2. Check QuickTime version number
    Open QuickTime Player, go to Help > About QuickTime (Windows) or QuickTime Player > About QuickTime Player (Mac). Alternatively, on Windows check the version in Add/Remove Programs details, or run 'qtdispatch.exe -version' if available in the QuickTime directory.
    Affected if Version is lower than 7.3 (for example, 7.2.x, 7.1.x, 7.0.x)
  3. Confirm PICT file handling capability is present
    QuickTime handles PICT files by default as part of its image parsing functionality. No additional components need to be enabled - the vulnerability exists in the core PICT parsing code that loads when QuickTime processes image files.
    Affected if QuickTime is installed and can open image files (PICT handling is built into QuickTime)
  4. Check operating system version
    On Windows: Right-click My Computer > Properties to see the OS version. On Mac: Run 'sw_vers' or see About This Mac.
    Affected if Running Windows XP, Windows Vista, or Mac OS X 10.3.9, 10.4.10, or 10.5 with QuickTime version below 7.3

The system is affected if QuickTime version is installed and is lower than 7.3 on any of the listed vulnerable operating system versions.

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 Apple QuickTime to version 7.3 or later. Until updated, avoid opening untrusted or unknown PICT image files from untrusted sources.

Recommended fix High confidence

QuickTime 7.3 or later

  1. Navigate to Apple's official QuickTime download page or use Software Update on Mac to check for updates
  2. Download QuickTime 7.3 or later for your operating system (Mac OS X or Windows)
  3. Close all applications that are using QuickTime
  4. Run the installer and follow the prompts to install the updated version
  5. Restart your computer if prompted to ensure the update is fully applied
  6. Verify the installed QuickTime version by opening QuickTime Player and checking About QuickTime Player

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
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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