dbcve.org
SafariWeb browser · Apple

CVE-2015-5819

MEDIUM · 6.8 CVSS v2.0 Published 2015-09-18
Fix available
A fix is available. Upgrade to after 12.2 or later.
See remediation →
77/100
Remediation priority · High
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 iOS before 9 and iTunes before 12.3, allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption and application crash) via a crafted web site, a different vulnerability than other WebKit CVEs listed in APPLE-SA-2015-09-16-1 and 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 · high confidence

Memory corruption vulnerability in WebKit, the browser engine used by Safari and UIWebView in iOS and iTunes. Remote attackers can exploit this by tricking users into visiting crafted malicious websites, potentially achieving arbitrary code execution or causing application crashes.

MitigationApply vendor-supplied patches by upgrading to iOS 9 or later and iTunes 12.3 or later. For enterprises, deploy updates through mobile device management (MDM) or software distribution tools.

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
Affected:<= 8.0.8
ItunesApplication
Affected:<= 12.2
Iphone OsOperating system
Affected:<= 8.4.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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Safari version on macOS
    Open Safari, click Safari menu > About Safari. Compare the version number to 8.0.8 or earlier.
    Affected if Version is 8.0.8 or earlier on macOS
  2. Check iTunes version on Windows or Mac
    Open iTunes, click Help > About iTunes. Compare the version number to 12.2 or earlier.
    Affected if Version is 12.2 or earlier
  3. Check iOS version on iPhone or iPad
    Open Settings > General > About on the iOS device. Look at the Version field. Compare to 8.4.1 or earlier.
    Affected if iOS version is 8.4.1 or earlier on the device
  4. Verify WebKit exposure
    Confirm that Safari or any app using UIWebView is actively used on the system or device.
    Affected if WebKit-based browsing (Safari or apps with embedded browsers) is used on an affected version

A system is affected if any installed Safari is 8.0.8 or earlier, iTunes is 12.2 or earlier, or iOS is 8.4.1 or earlier, and the WebKit browser component is accessible to users.

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.

From vendor data
Upgrade available Upgrade to a release after 12.2
Interim mitigation

Apply vendor-supplied patches by upgrading to iOS 9 or later and iTunes 12.3 or later. For enterprises, deploy updates through mobile device management (MDM) or software distribution tools.

Fix this in Safari Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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