dbcve.org
ItunesApplication · Apple

CVE-2013-0999

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

Memory corruption vulnerability in WebKit rendering engine used by Apple iTunes allows remote attackers to execute arbitrary code or cause application crashes via man-in-the-middle attacks during iTunes Store browsing sessions.

MitigationUpdate Apple iTunes to version 11.0.3 or later to obtain the patched WebKit component; ensure network security to reduce MITM attack surface during browsing.

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
    On Windows, open Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\iTunes.exe, or run 'wmic product get name,version' in Command Prompt. On macOS, check /Applications for iTunes.app.
    Affected if iTunes is not found on the system, the system is not affected.
  2. Retrieve installed iTunes version
    On Windows, check the Version value in the registry path above, or right-click iTunes in Start menu and select Properties. On macOS, right-click iTunes.app and select Get Info.
    Affected if Unable to determine version, manual verification required.
  3. Compare version against affected ranges
    Compare your installed version to: Apple iTunes 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 earlier.
    Affected if Your installed version matches any of these specific versions or is 11.0.2 or earlier, your environment falls within the affected range.
  4. Assess iTunes Store browsing usage
    Check if iTunes is configured to access the iTunes Store. Open iTunes, go to Store menu and verify if Store features are enabled or if the user has previously browsed/purchased content from the Store.
    Affected if iTunes Store browsing is never used and network traffic to Apple's servers is blocked, the exploitation vector is not accessible.

You are affected if iTunes is installed with a version matching the affected list (4.x series or 11.0.2 and below) AND iTunes Store browsing occurs over a network where MITM attacks are theoretically 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 Apple iTunes to version 11.0.3 or later to obtain the patched WebKit component; ensure network security to reduce MITM attack surface during browsing.

Recommended fix High confidence

iTunes 11.0.3 or later; iOS 6.1.5 or later (or latest available iOS version)

  1. 1. For iTunes users: Open iTunes and check the current version (Help > About iTunes)
  2. 2. If running iTunes version 11.0.2 or earlier, download and install iTunes 11.0.3 or later from https://www.apple.com/itunes/
  3. 3. For iPhone OS (iOS) users: Navigate to Settings > General > Software Update on the device
  4. 4. If running iOS version 6.1.4 or earlier, download and install the latest available iOS version through the software update feature
  5. 5. After updating, verify the new version number in the respective About settings
Caveat Major iOS upgrades (e.g., from iOS 6 to iOS 7) may introduce UI changes and require app compatibility verification

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
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-0999 — 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-0999 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