SafariWeb browser · Apple
CVE-2019-8823
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 13.2 and iPadOS 13.2, tvOS 13.2, Safari 13.0.3, iTunes for Windows 12.10.2, iCloud for Windows 11.0, iCloud for Windows 7.15. 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 · moderate confidenceMemory corruption vulnerability in WebKit affecting iOS, iPadOS, tvOS, Safari, iTunes, and iCloud for Windows. Processing maliciously crafted web content can lead to arbitrary code execution due to improper memory handling during rendering.
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
< 13.0.3< 7.15>= 10.0, <= 10.4< 12.10.2< 13.2< 13.2< 13.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
- 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.
-
Identify the Apple product using WebKitDetermine which of these is installed: Safari browser, iTunes, iCloud for Windows, or an iOS/iPadOS/tvOS device. For Windows, check Add/Remove Programs or the application About dialog. For iOS/iPadOS/tvOS, go to Settings > General > About.Affected if Any of these products are present on the system or device
-
Check Safari versionIn Safari, go to Safari > About Safari (Mac) or Help > About Safari (Windows). Compare the version number to 13.0.3. Versions below 13.0.3 are affected.Affected if Safari version is lower than 13.0.3
-
Check iTunes versionOpen iTunes and go to Help > About iTunes. Compare the version to 12.10.2. Versions below 12.10.2 are affected.Affected if iTunes version is lower than 12.10.2
-
Check iCloud for Windows versionOpen iCloud for Windows, click the menu icon, and select About iCloud. Compare version to 7.15 or 11.0. Versions below 7.15, or between 10.0 and 10.4 inclusive, are affected.Affected if iCloud for Windows version is below 7.15, or between 10.0 and 10.4 inclusive
-
Check iOS/iPadOS/tvOS versionOn the device, go to Settings > General > About and note the version number. iOS and iPadOS versions below 13.2 are affected. tvOS versions below 13.2 are affected.Affected if iOS, iPadOS, or tvOS version is lower than 13.2
The environment is affected if any installed Apple product (Safari, iTunes, iCloud for Windows, iOS, iPadOS, or tvOS) has a version lower than the fixed versions listed in the affected ranges and processes untrusted web content.
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.1512.10.213.0.3
Apply vendor updates: iOS 13.2/iPadOS 13.2, tvOS 13.2, Safari 13.0.3, iTunes 12.10.2, iCloud for Windows 11.0 or 7.15. Disable JavaScript in untrusted web contexts as a defense-in-depth measure until patches are applied.
Fix this in Safari
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-8823 — 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-8823 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