SafariWeb browser · Apple
CVE-2019-8773
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 Safari 13.0.1, iOS 13.1 and iPadOS 13.1, iCloud for Windows 10.7, iCloud for Windows 7.14, tvOS 13, watchOS 6, iTunes 12.10.1 for Windows. 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 vulnerabilities in WebKit (Apple's browser engine) that can be triggered by processing maliciously crafted web content, potentially allowing arbitrary code execution. The issues were addressed with improved memory handling in the affected Apple products.
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.1< 7.14>= 10.0, < 10.7< 12.10.1< 13.1< 13.1< 13< 6.0CVSS 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 Safari version on macOSOpen Safari, click Safari menu > About Safari, or run 'safariVersion' in TerminalAffected if Version is earlier than 13.0.1
-
Check iOS or iPadOS versionGo to Settings > General > About on the deviceAffected if Version is earlier than 13.1
-
Check tvOS versionGo to Settings > General > About on Apple TVAffected if Version is earlier than 13.0
-
Check watchOS versionOpen the Watch app on iPhone, go to My Watch > General > AboutAffected if Version is earlier than 6.0
-
Check iTunes version on WindowsOpen iTunes, go to Help > About iTunesAffected if Version is earlier than 12.10.1
-
Check iCloud for Windows versionOpen iCloud, click the menu icon > About iCloud, or check Programs and Features in Control PanelAffected if Version is earlier than 7.14 or between 10.0 and 10.6 (inclusive)
A device or software installation is affected if its version falls below the fixed release for that product (Safari 13.0.1, iOS/iPadOS 13.1, tvOS 13, watchOS 6, iTunes 12.10.1, or iCloud for Windows 7.14/10.7) and uses WebKit to process 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 data6.07.1410.7
Apply the available Apple security updates (Safari 13.0.1, iOS/iPadOS 13.1, tvOS 13, watchOS 6, iCloud for Windows 10.7/7.14, iTunes 12.10.1) to all affected devices and software installations.
Fix this in Safari
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2019-8773 — 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-8773 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