dbcve.org
Iphone OsOperating system · Apple

CVE-2013-1006

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 rendering engine used by Apple iTunes versions prior to 11.0.3 allows man-in-the-middle attackers on the network path to achieve arbitrary code execution or cause denial of service via vectors related to iTunes Store browsing.

MitigationUpdate Apple iTunes to version 11.0.3 or later to obtain the patched WebKit component. Users should avoid browsing the iTunes Store on untrusted networks 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
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. Identify the installed iTunes version
    Open iTunes, then go to Help > About iTunes. The version number is displayed in the dialog box. On Windows, you can also right-click the iTunes executable, select Properties, and view the Details tab.
    Affected if The version is any of: 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.1, or any version 11.0.2 or lower, including 11.0, 11.0.1, 11.0.2.
  2. Confirm iTunes Store browsing capability
    Launch iTunes and verify whether the iTunes Store feature is accessible. Look for the Store menu option or the iTunes Store icon in the source list on the left pane.
    Affected if The iTunes Store is present and accessible in the iTunes application.
  3. Determine if WebKit is used for Store browsing
    When browsing the iTunes Store, the application uses its internal WebKit rendering engine to display content. This is the component vulnerable to memory corruption.
    Affected if iTunes Store browsing is performed, which triggers the WebKit rendering for Store content.
  4. Check for iTunes on iOS devices (if applicable)
    For iPhone OS devices, check the iOS version by going to Settings > General > About > Version. This CVE also affects iPhone OS versions up to and including 6.1.4, as well as specific older versions 1.0.0 through 2.0.0.
    Affected if The iOS version is 6.1.4 or lower, or exactly matches 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.

You are affected if you are running any vulnerable version of iTunes (4.x through 11.0.2) or iPhone OS (1.x through 6.1.4) AND you use the iTunes Store browsing feature, because the vulnerability lies in the WebKit component used during Store navigation.

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. Users should avoid browsing the iTunes Store on untrusted networks until patched.

Recommended fix High confidence

iTunes 11.0.3 or later; iOS 7.0 or later for iPhone OS devices

  1. Upgrade to iTunes 11.0.3 or later, which contains the fixed WebKit component
  2. For iPhone OS (iOS) devices, upgrade to a version higher than 6.1.4 (such as iOS 7.0 or later) to ensure compatibility with the fixed iTunes version
  3. After upgrading, verify the iTunes installation by checking Help > About iTunes to confirm the version is 11.0.3 or higher
  4. Ensure SSL/TLS certificate validation is enabled in your network environment to protect against man-in-the-middle attacks when browsing the iTunes Store
Caveat Upgrading iTunes may require Windows 7 or later or OS X 10.6.8 or later; older iOS devices may not support newer iOS versions

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