dbcve.org
Iphone OsOperating system · Apple

CVE-2019-6211

HIGH · 8.8 CVSS v3.0 Published 2019-03-05
Fix available
A fix is available. Upgrade to 10.14.3 / 12.1.3 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
A memory corruption issue was addressed with improved state management. This issue is fixed in iOS 12.1.3, macOS Mojave 10.14.3. 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 confidence

This is a memory corruption vulnerability in WebKit, Apple's browser rendering engine used by Safari and UIWebView. The issue stems from improper state management during web content processing. Successful exploitation allows arbitrary code execution on the affected device when a user processes maliciously crafted web content.

MitigationApply the vendor-supplied patches by updating to iOS 12.1.3 or later and macOS Mojave 10.14.3 or later. Until patches are applied, users should avoid visiting untrusted or suspicious websites.

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
Iphone OsOperating system
Affected:< 12.1.3
Mac Os XOperating system
Affected:< 10.14.3

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
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/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 checks

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

  1. Identify the operating system
    Check if the system is running iOS or macOS by looking at the device or system information.
    Affected if System is an Apple device running iOS or macOS.
  2. Check the installed iOS version
    On an iPhone or iPad, go to Settings > General > About and look at the Version field. Compare the version number to 12.1.3.
    Affected if iOS version is lower than 12.1.3.
  3. Check the installed macOS version
    On a Mac, click the Apple menu > About This Mac. The version is displayed below the macOS name. Compare to 10.14.3.
    Affected if macOS version is lower than 10.14.3.
  4. Confirm WebKit usage
    Determine if Safari or any application using UIWebView (iOS) or WebKit (macOS) is used to browse or render web content.
    Affected if Safari or a WebKit-based application processes web content on an affected system.

A user is affected if they are running iOS versions below 12.1.3 or macOS versions below 10.14.3 AND use Safari or a WebKit-based application to process web content.

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 10.14.3 / 12.1.3 or later
Fixed in 10.14.312.1.3
Interim mitigation

Apply the vendor-supplied patches by updating to iOS 12.1.3 or later and macOS Mojave 10.14.3 or later. Until patches are applied, users should avoid visiting untrusted or suspicious websites.

Fix this in Iphone Os Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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