dbcve.org
SafariWeb browser · Apple

CVE-2018-4309

MEDIUM · 6.1 CVSS v3.0 Published 2019-04-03
Fix available
A fix is available. Upgrade to 7.7 / 12 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 affected versions prior to iOS 12, tvOS 12, Safari 12, iTunes 12.9 for Windows, iCloud for Windows 7.7.

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

A cross-site scripting (XSS) vulnerability in Safari existed due to insufficient URL validation, allowing malicious URLs to inject and execute arbitrary JavaScript in the context of a user's browser session.

MitigationApply vendor-provided updates: upgrade to iOS 12+, tvOS 12+, Safari 12+, iTunes 12.9+ for Windows, or iCloud for Windows 7.7+ to obtain the improved URL validation fix.

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
Iphone OsOperating system
Affected:< 12.0
TvosOperating system
Affected:< 12
IcloudApplication
Affected:< 7.7
ItunesApplication
Affected:< 12.9

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. Identify the Apple product in use
    Determine which Apple application or device you are running: Safari browser, iOS device, tvOS device, iTunes for Windows, or iCloud for Windows.
    Affected if The product is Safari, iOS, tvOS, iTunes, or iCloud.
  2. Check Safari version
    In Safari, go to Safari > About Safari to view the version number.
    Affected if The version is below 12.0 (e.g., 11.x or earlier).
  3. Check iOS version
    On the iOS device, go to Settings > General > About to view the iOS version.
    Affected if The version is below 12.0 (e.g., 11.x or earlier).
  4. Check tvOS version
    On the Apple TV, go to Settings > General > About to view the tvOS version.
    Affected if The version is below 12.0 (e.g., 11.x or earlier).
  5. Check iTunes version
    In iTunes on Windows, go to Help > About iTunes to view the version number.
    Affected if The version is below 12.9.
  6. Check iCloud for Windows version
    In iCloud for Windows, click the iCloud icon and select About iCloud to view the version number.
    Affected if The version is below 7.7.

You are affected if any installed Apple product (Safari, iOS, tvOS, iTunes, or iCloud for Windows) has a version number lower than the corresponding fixed version (Safari 12+, iOS 12+, tvOS 12+, iTunes 12.9+, iCloud 7.7+).

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 7.7 / 12 / 12.0 or later
Fixed in 7.71212.0
Interim mitigation

Apply vendor-provided updates: upgrade to iOS 12+, tvOS 12+, Safari 12+, iTunes 12.9+ for Windows, or iCloud for Windows 7.7+ to obtain the improved URL validation fix.

Fix this in Safari Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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