dbcve.org
SafariWeb browser · Apple

CVE-2019-6228

MEDIUM · 6.1 CVSS v3.0 Published 2019-03-05
Fix available
A fix is available. Upgrade to 12.0.3 / 12.1.3 or later.
See remediation →
68/100
Remediation priority · Elevated
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 cross-site scripting issue existed in Safari. This issue was addressed with improved URL validation. This issue is fixed in iOS 12.1.3, Safari 12.0.3. Processing maliciously crafted web content may lead to a cross site scripting attack.

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 cross-site scripting (XSS) vulnerability in Safari's web content processing. Due to insufficient URL validation, maliciously crafted web content can inject and execute arbitrary JavaScript in the context of a victim's session, potentially stealing cookies, session tokens, or performing actions on behalf of the user.

MitigationUpdate Safari to version 12.0.3 or later (iOS 12.1.3 or later for mobile). Users should avoid visiting untrusted websites until the update is applied.

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
Affected:< 12.0.3
Iphone OsOperating system
Affected:< 12.1.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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

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. Check Safari version on macOS
    Open Safari, click Safari in the menu bar, then select About Safari. The version number is displayed next to 'Safari'.
    Affected if The version shown is earlier than 12.0.3 (for example, 12.0.2, 12.0.1, 12.0, or any 11.x version)
  2. Check iOS version on iPhone or iPad
    Go to Settings > General > About. The version number is displayed next to 'Version'.
    Affected if The version shown is earlier than 12.1.3 (for example, 12.1.2, 12.1.1, 12.1, 12.0.x, or any 11.x version)
  3. Confirm the vulnerability scope
    Understand that this is a client-side XSS flaw triggered by visiting malicious web content. The vulnerability exists in Safari's web content processing when handling certain URLs.
    Affected if You use an affected Safari or iOS version AND you browse the web (the exploit requires viewing specially crafted web content)

You are affected if you are running Safari versions before 12.0.3 on macOS or iOS versions before 12.1.3 on iPhone/iPad, and you browse the web where malicious content could be loaded.

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

Update Safari to version 12.0.3 or later (iOS 12.1.3 or later for mobile). Users should avoid visiting untrusted websites until the update is applied.

Fix this in Safari Scoped from the published advisory
  • Consultation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
3.0 hours of engineering $750
Get the upgrade done

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 locally
dbcve dependency scanner

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