dbcve.org
ItunesApplication · Apple

CVE-2013-1007

HIGH · 9.3 CVSS v2.0 Published 2013-05-20
Fix available
A fix is available. Upgrade to after 11.0.2 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
WebKit, as used in Apple iTunes before 11.0.3, allows man-in-the-middle attackers to execute arbitrary code or cause a denial of service (memory corruption and application crash) via vectors related to iTunes Store browsing, a different vulnerability than other WebKit CVEs listed in APPLE-SA-2013-05-16-1.

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 · moderate confidence

WebKit rendering engine vulnerability in iTunes before 11.0.3 allows man-in-the-middle attackers to achieve arbitrary code execution or cause memory corruption leading to application crashes during iTunes Store browsing sessions.

MitigationUpdate iTunes to version 11.0.3 or later to address the WebKit vulnerability. Avoid browsing iTunes Store on untrusted networks to reduce MITM attack exposure until patched.

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:<= 11.0.2= 4.0.0= 4.0.1= 4.1.0= 4.2.0= 4.5= 4.5.0= 4.6= 4.6.0= 4.7= 4.7.0= 4.7.1
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. Verify iTunes installation
    Open iTunes and navigate to Help > About iTunes (Windows) or iTunes > About iTunes (Mac). The version number will be displayed in the About dialog.
    Affected if iTunes is installed and the displayed version matches any of these: 4.0.0, 4.0.1, 4.1.0, 4.2.0, 4.5, 4.5.0, 4.6, 4.6.0, 4.7, 4.7.0, 4.7.1, or is 11.0.2 or lower
  2. Check iTunes version via file properties (Windows)
    Right-click the iTunes.exe file (typically in C:\Program Files\iTunes or C:\Program Files (x86)\iTunes), select Properties, and view the Details tab to see the Product Version.
    Affected if The Product Version shown is 11.0.2 or lower, or matches any of these specific versions: 4.0.0, 4.0.1, 4.1.0, 4.2.0, 4.5, 4.5.0, 4.6, 4.6.0, 4.7, 4.7.0, 4.7.1
  3. Confirm vulnerable feature is in use
    Determine whether the iTunes Store browsing feature is actively used. Open iTunes and check if the iTunes Store section is accessible or has been accessed (sign-in to Store, browse for media content).
    Affected if The iTunes Store feature is accessible or has been used, as the vulnerability is triggered during iTunes Store browsing sessions
  4. Check iPhone OS version on device (if applicable)
    On an iOS device, go to Settings > General > About and note the Version number. For iPhone OS, versions up to and including 6.1.4 are affected.
    Affected if The iOS device runs iPhone OS 6.1.4 or lower, or runs versions 1.0.0 through 2.0.0 as listed in the affected versions

You are affected if iTunes version 11.0.2 or lower, or any of the specific older versions (4.x through 4.7.1) is installed AND the iTunes Store browsing feature is accessible or used on that system.

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

Update iTunes to version 11.0.3 or later to address the WebKit vulnerability. Avoid browsing iTunes Store on untrusted networks to reduce MITM attack exposure until patched.

Recommended fix High confidence

iTunes 11.0.3 or later (or migrate to Apple Music app on macOS 10.15+)

  1. Upgrade iTunes to version 11.0.3 or later to resolve the WebKit vulnerability
  2. If running on Windows, download the latest iTunes version from Apple's official website or Microsoft Store
  3. If running on macOS, iTunes was replaced by the Music app in macOS 10.15 (Catalina) and later; consider migrating to the Music app
Caveat iTunes was discontinued in 2023; Windows users should migrate to Apple Music app; very old iPhone OS devices (1.x) are no longer supported and cannot run modern iTunes versions

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

Fix this in Itunes 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-2013-1007 — 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-1007 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