dbcve.org
Iphone OsOperating system · Apple

CVE-2013-1004

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 memory corruption vulnerability in WebKit, the rendering engine used by Apple iTunes before version 11.0.3, allows man-in-the-middle attackers to inject malicious code during iTunes Store browsing sessions. Successful exploitation enables arbitrary code execution or causes memory corruption leading to application crashes.

MitigationUpdate iTunes to version 11.0.3 or later to obtain the patched WebKit component. Avoid browsing the iTunes Store on untrusted networks to reduce MITM exposure.

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

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 installed iTunes version on Windows
    Open iTunes, go to Help > About iTunes, or right-click the iTunes executable, select Properties, and view the File Version. Alternatively, check the registry key: HKLM\SOFTWARE\Apple Computer, Inc.\iTunes\Version
    Affected if The version displayed is 11.0.2 or earlier, or matches any of these vulnerable 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, or 4.7.1
  2. Check iOS version on iPhone or iPad
    On the iOS device, go to Settings > General > About > Version
    Affected if The version is 6.1.4 or lower, or matches exactly: 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, or 2.0.0
  3. Confirm WebKit component is in use
    Verify that iTunes has WebKit available. On Windows, check for WebKit DLL files in the iTunes installation directory, typically at C:\Program Files\iTunes\ or C:\Program Files (x86)\iTunes\
    Affected if WebKit.dll exists in the iTunes program folder, confirming the vulnerable rendering engine component is present
  4. Determine if iTunes Store browsing is accessible
    Launch iTunes and check if the iTunes Store section is visible in the iTunes window. The vulnerability is triggered during iTunes Store browsing sessions
    Affected if The iTunes Store link or icon is present and functional, indicating the browsing feature that triggers the vulnerable WebKit code path is enabled

You are affected if you are running any iTunes version 11.0.2 or earlier, or any iOS version 6.1.4 or lower, and the iTunes Store feature is accessible on an untrusted network where MITM attacks are possible.

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 obtain the patched WebKit component. Avoid browsing the iTunes Store on untrusted networks to reduce MITM exposure.

Recommended fix High confidence

iTunes 11.0.3 or later

  1. Back up your iTunes library and any important data before upgrading
  2. Download iTunes 11.0.3 or later from Apple's official website (apple.com/itunes)
  3. Install the updated version of iTunes by running the installer
  4. Follow the on-screen prompts to complete the installation
  5. Launch iTunes and verify the application runs without memory corruption errors
  6. Confirm that iTunes Store browsing functionality works properly
Caveat Upgrading iTunes may include UI changes and feature updates from the 11.x release; ensure compatible device synchronization

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

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

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