dbcve.org
SafariWeb browser · Apple

CVE-2018-4137

HIGH · 7.5 CVSS v3.0 Published 2018-04-03
Fix available
A fix is available. Upgrade to 11.1 / 11.3 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
An issue was discovered in certain Apple products. iOS before 11.3 is affected. Safari before 11.1 is affected. The issue involves the "Safari Login AutoFill" component. It allows remote attackers to read autofilled data by leveraging lack of a user-confirmation requirement.

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

The Safari Login AutoFill component in iOS before 11.3 and Safari before 11.1 does not require user confirmation before autofilling and exposing stored credentials, allowing remote attackers to read sensitive autofilled data through malicious web pages without any user interaction.

MitigationUpgrade to iOS 11.3 or later and Safari 11.1 or later to obtain the vendor patch that adds user-confirmation requirement before autofilling credentials.

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:< 11.1
Iphone OsOperating system
Affected:< 11.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
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 > Safari menu > About Safari. Compare the version number to 11.1 (e.g., 11.0.x or earlier is affected).
    Affected if Safari version is below 11.1
  2. Check iOS version on iPhone/iPad
    Go to Settings > General > About > Version. Compare the version to 11.3 (e.g., 11.2.x or earlier is affected).
    Affected if iOS version is below 11.3
  3. Verify if Password AutoFill is enabled
    On iOS: Settings > Safari > AutoFill > ensure Passwords is toggled ON. On macOS: Safari > Preferences > AutoFill > verify 'User names and passwords' is checked.
    Affected if Password AutoFill is enabled and the Safari/iOS version is in the vulnerable range

The environment is affected if Safari is below 11.1 (or iOS is below 11.3) AND Password AutoFill is enabled, allowing malicious webpages to silently autofill stored credentials without user interaction.

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 11.1 / 11.3 or later
Fixed in 11.111.3
Interim mitigation

Upgrade to iOS 11.3 or later and Safari 11.1 or later to obtain the vendor patch that adds user-confirmation requirement before autofilling credentials.

Fix this in Safari Scoped from the published advisory
  • Consultation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.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-2018-4137 — 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-4137 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