CVE-2019-6219
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 · uneditedA denial of service issue was addressed with improved validation. This issue is fixed in iOS 12.1.3, macOS Mojave 10.14.3, watchOS 5.1.3. Processing a maliciously crafted message may lead to a denial of service.
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 confidenceThis is a denial of service vulnerability in Apple's message processing components across iOS, macOS, and watchOS. The vulnerability allows a remote attacker to cause a DoS condition by sending a maliciously crafted message to a targeted device. The fix was implemented through improved input validation.
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< 12.1.3< 10.14.3< 5.1.3CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 your Apple device typeDetermine whether the device is an iPhone/iPad/iPod (iOS), a Mac (macOS), or an Apple Watch (watchOS). This will determine which OS version to check.Affected if Device runs iOS, macOS, or watchOS and processes messages
-
Check installed iOS version on iPhone or iPadGo to Settings > General > About on the device and note the version number displayed next to 'Version'. Compare this to the affected range: anything below 12.1.3 is vulnerable.Affected if iOS version is lower than 12.1.3
-
Check installed macOS version on MacClick the Apple menu > About This Mac. The version number appears below the macOS name (such as Mojave). Compare to the affected range: anything below 10.14.3 is vulnerable.Affected if macOS version is lower than 10.14.3
-
Check installed watchOS version on Apple WatchOpen the Watch app on your paired iPhone, go to My Watch > General > About, and note the watchOS version. Compare to the affected range: anything below 5.1.3 is vulnerable.Affected if watchOS version is lower than 5.1.3
-
Confirm messaging feature is in useVerify that iMessage (on iOS/macOS) or the Messages app is enabled and configured on the device. On iOS: Settings > Messages is turned on. On macOS: Open Messages app and ensure an account is signed in.Affected if iMessage or Messages is enabled and active on the device
You are affected if your device runs an unpatched iOS version below 12.1.3, macOS below 10.14.3, or watchOS below 5.1.3, and you have messaging services 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 data5.1.310.14.312.1.3
Apply the vendor-supplied patches by updating iOS devices to 12.1.3 or later, macOS devices to Mojave 10.14.3 or later, and watchOS devices to 5.1.3 or later.
- Consultation1.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-2019-6219 — 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-6219 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