SafariWeb browser · Apple
CVE-2015-5808
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 · uneditedWebKit, as used in Apple iTunes before 12.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-2015-09-16-3.
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 confidenceMemory corruption vulnerability in WebKit rendering engine, as embedded in Apple iTunes versions prior to 12.3. A man-in-the-middle attacker on the network path during iTunes Store browsing can trigger memory corruption leading to arbitrary code execution or application crash (denial of service).
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
SafariWeb browser
<= 8.0.8<= 12.2CVSS 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
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
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 checksWork through these to decide whether this CVE applies to you.
-
Check installed iTunes version on WindowsOpen iTunes and go to Help > About iTunes, or run PowerShell: Get-ItemProperty 'C:\Program Files\iTunes\iTunes.exe' | Select-Object VersionInfoAffected if The version shown is 12.2 or lower, indicating a vulnerable WebKit component
-
Check Safari version on macOSOpen Safari > Safari menu > About Safari, or run: /Applications/Safari.app/Contents/MacOS/Safari --versionAffected if The version is 8.0.8 or lower, indicating a vulnerable WebKit component
-
Verify if iTunes is configured to access the iTunes StoreOpen iTunes and check if the iTunes Store is accessible or visible in the iTunes window sidebarAffected if The iTunes Store is accessible and the installed iTunes version is 12.2 or lower, making the exploit path viable
-
Check macOS system version for Safari contextOpen Apple menu > About This Mac to see the macOS versionAffected if Running macOS versions that shipped with Safari 8.0.8 or earlier (such as OS X Yosemite 10.10.5 or earlier)
You are affected if you have iTunes version 12.2 or earlier on Windows, or Safari version 8.0.8 or earlier on macOS, AND you browse the iTunes Store on untrusted networks where a MITM attack could occur.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpdate Apple iTunes to version 12.3 or later to obtain the patched WebKit component. As a workaround, avoid browsing the iTunes Store on untrusted networks to reduce MITM attack exposure.
Fix this in Safari
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2015-5808 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-5808 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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