dbcve.org
Iphone OsOperating system · Apple

CVE-2013-1008

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

Memory corruption vulnerability in WebKit as embedded in Apple iTunes versions prior to 11.0.3 allows MITM attackers to achieve arbitrary code execution or cause denial of service when users browse the iTunes Store. The vulnerability stems from improper handling of web content during store browsing sessions.

MitigationUpdate Apple iTunes to version 11.0.3 or later to obtain the patched WebKit component. For enterprise environments, deploy the update via patch management systems and verify completion across affected clients.

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 Windows Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Apple Computer, Inc.\iTunes\, or run 'reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Apple Computer, Inc.\iTunes" /v Version'
    Affected if The Version value is 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 (such as 8.0, 9.0, 10.0, 11.0, 11.0.1, 11.0.2)
  2. Check installed iTunes version on macOS
    Open iTunes, go to Help > About iTunes, or run 'defaults read /Applications/iTunes.app/Contents/Info CFBundleVersion' in Terminal
    Affected if The version shown is 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 (such as 8.0, 9.0, 10.0, 11.0, 11.0.1, 11.0.2)
  3. Check iOS device version for iPhone OS
    Connect iOS device to computer, open iTunes or check Settings > General > About on the device, or use Apple Configurator or third-party MDM tools
    Affected if The iOS version is 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, or any version <= 6.1.4 (such as 3.0, 4.0, 5.0, 6.0, 6.1)

A system is affected if iTunes version is <= 11.0.2 or iPhone OS version is <= 6.1.4, AND the user browses the iTunes Store (the attack requires the WebKit component to process malicious web content during store sessions).

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 Apple iTunes to version 11.0.3 or later to obtain the patched WebKit component. For enterprise environments, deploy the update via patch management systems and verify completion across affected clients.

Recommended fix High confidence

iTunes 11.0.3 or later (latest available version recommended)

  1. Open iTunes on your Windows or Mac computer
  2. Check the current version by going to Help > About iTunes
  3. Download the latest version of iTunes from Apple's official website (apple.com/itunes) or through Microsoft Store (Windows 10+)
  4. Install the updated version which includes the security fix for WebKit vulnerability CVE-2013-1008
  5. Verify the installation by checking Help > About iTunes shows version 11.0.3 or later
Caveat iTunes 11.0.3 requires Windows 7 or later, or Mac OS X 10.6.8 or later; older operating systems may need to use an older iTunes version

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