CreatorApplication · Roxio

CVE-2009-1566

HIGH · 9.3 CVSS v2.0 Published 2009-12-03
Fix available
A fix is available. Upgrade to after 9.0.136 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
Integer overflow in Roxio Easy Media Creator 9.0.136, and Roxio Creator 2010 before SP1, might allow remote attackers to execute arbitrary code via an image with crafted dimensions.

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

Integer overflow vulnerability in Roxio Easy Media Creator 9.0.136 and Creator 2010 before SP1 allows remote code execution when processing images with crafted, specially crafted dimensions that overflow integer calculations.

MitigationUpdate Roxio Creator to SP1 or later which contains the vendor patch; avoid opening images from untrusted sources until the patch is applied.

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
CreatorApplication
Affected:<= 9.0.136
Easy Media CreatorApplication
Affected:= 9.0.136

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 Roxio product installation
    Check installed programs list for Roxio Creator or Roxio Easy Media Creator
    Affected if Either product is present on the system
  2. Determine installed version
    Locate the installed version number through program properties, registry, or the About section within the application
    Affected if Version is 9.0.136 or earlier for either product
  3. Confirm product is Roxio Creator 2010
    If the product name includes Creator 2010, check if Service Pack 1 has been applied
    Affected if Running Creator 2010 without Service Pack 1
  4. Verify image processing usage
    Determine if the software has been used to process image files
    Affected if Images have been processed using the affected software version

The system is affected if Roxio Creator version 9.0.136 or earlier, or Roxio Creator 2010 without SP1, is installed and has been used to process images.

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 9.0.136
Interim mitigation

Update Roxio Creator to SP1 or later which contains the vendor patch; avoid opening images from untrusted sources until the patch is applied.

Recommended fix Moderate confidence

Roxio Creator 2010 SP1 or later; Roxio Easy Media Creator to latest supported version

  1. 1. Identify the exact Roxio product and version installed (Creator or Easy Media Creator)
  2. 2. For Roxio Creator 2010: Upgrade to Service Pack 1 (SP1) or later to remediate the integer overflow vulnerability
  3. 3. For Roxio Easy Media Creator 9.0.136: Contact Roxio customer support to inquire about available patches or updates for this specific version
  4. 4. If no official patch is available for Easy Media Creator 9.0.136, consider upgrading to a newer supported version of the software
  5. 5. Apply the upgrade following standard installation procedures
  6. 6. Verify the installation and test that the software functions normally
Caveat Older software versions may have compatibility issues with newer operating systems - verify system requirements before upgrading

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

Fix this in Creator Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-2009-1566 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