SafariWeb browser · Apple
CVE-2019-8681
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 · uneditedMultiple memory corruption issues were addressed with improved memory handling. This issue is fixed in iOS 12.4, macOS Mojave 10.14.6, tvOS 12.4, Safari 12.1.2, iTunes for Windows 12.9.6, iCloud for Windows 7.13, iCloud for Windows 10.6. Processing maliciously crafted web content may lead to arbitrary code execution.
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 confidenceMemory corruption vulnerability in WebKit affecting Safari and other Apple products. Processing maliciously crafted web content allows attackers to achieve arbitrary code execution via corrupted memory handling.
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
< 12.1.2< 7.13>= 10.0, < 10.6< 12.9.6< 12.4< 10.14.6< 12.4CVSS 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
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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 macOS versionOpen Terminal and run 'sw_vers' or go to Apple menu > About This Mac to view the macOS version numberAffected if The version shown is earlier than 10.14.6 (Mojave) and Safari or other WebKit-based browsers are used
-
Check iOS/tvOS versionOn iOS, go to Settings > General > About > Version. On tvOS, go to Settings > About > VersionAffected if The version is earlier than 12.4 and the browser app is used
-
Check Safari versionOpen Safari, then go to Safari menu > About Safari to view the version numberAffected if The version is earlier than 12.1.2 and Safari is used to browse untrusted websites
-
Check iTunes version (Windows or macOS)Open iTunes, then go to Help > About iTunes to view the version numberAffected if The version is earlier than 12.9.6 and iTunes is used (iTunes includes WebKit for some features)
-
Check iCloud for Windows versionOpen iCloud, then go to the settings or About section to view the version numberAffected if The version is earlier than 7.13 (or between 10.0 and 10.5) and iCloud is installed
-
Verify JavaScript is enabled in browsersIn Safari, go to Safari > Preferences > Security and check 'Enable JavaScript'. In other WebKit browsers, check their security settingsAffected if JavaScript is enabled in Safari or other WebKit-based browsers that process untrusted web content
You are affected if any Apple product you have installed matches the unpatched version ranges AND you use the browser or process web content with JavaScript enabled.
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 data7.1310.610.14.6
Apply vendor patches: update to iOS 12.4+, macOS Mojave 10.14.6+, tvOS 12.4+, Safari 12.1.2+, iTunes 12.9.6+, iCloud for Windows 7.13/10.6+. Disable JavaScript in untrusted browsers as temporary mitigation.
Fix this in Safari
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-8681 — 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-2019-8681 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