dbcve.org
ItunesApplication · Apple

CVE-2013-1002

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

A man-in-the-middle vulnerability in WebKit as used by Apple iTunes before version 11.0.3 allows remote attackers to execute arbitrary code or cause memory corruption and application crashes via vectors related to iTunes Store browsing. The attacker must be positioned on the same network as the victim to intercept and modify traffic during iTunes Store sessions.

MitigationUpgrade iTunes to version 11.0.3 or later. Avoid browsing the iTunes Store on untrusted networks, or use a VPN to protect traffic from MITM interception.

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. Determine iTunes version on Windows
    Open Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Apple Computer, Inc.\iTunes, or right-click the iTunes.exe file and select Properties > Details to view the File Version.
    Affected if The installed version matches one listed in the affected 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, or any version 11.0.2 or lower.
  2. Determine iTunes version on macOS
    Open iTunes and select iTunes > About iTunes from the menu bar, or view the iTunes.app package contents and check the Info.plist for the CFBundleShortVersionString.
    Affected if The installed version matches one listed in the affected versions: 4.0.0 through 4.7.1, or any version 11.0.2 or lower.
  3. Identify if iTunes Store browsing is used
    Launch iTunes and observe whether the user accesses the iTunes Store feature by clicking the Store icon in the iTunes window sidebar or header.
    Affected if The iTunes Store feature is accessible and has been used, as this is the vulnerable vector through which MITM traffic is intercepted.
  4. Check for iTunes process related to Store connections
    While iTunes is running, use Task Manager (Windows) or Activity Monitor (macOS) to inspect network connections established by iTunes.exe or iTunes.app, particularly to Apple servers related to Store traffic.
    Affected if Active network connections exist to iTunes Store domains while the affected iTunes version is running.

You are affected if you are running any iTunes version 11.0.2 or earlier, or any of the specific older versions listed (4.0.0 through 4.7.1), and you use or have used the iTunes Store browsing feature on any network.

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

Upgrade iTunes to version 11.0.3 or later. Avoid browsing the iTunes Store on untrusted networks, or use a VPN to protect traffic from MITM interception.

Recommended fix High confidence

iTunes 11.0.3 (or later)

  1. Upgrade Apple iTunes to version 11.0.3 or later to resolve the WebKit vulnerability
  2. For iPhone OS (iOS) devices, ensure the device is updated to a version beyond iOS 6.1.4 through the device's Settings > General > Software Update
Caveat Minor: Upgrading iTunes may require the corresponding iTunes installation package and may prompt for restart

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

Fix this in Itunes 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 the upgrade done

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-2013-1002 — 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-1002 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