SafariWeb browser · Apple
CVE-2017-2385
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 · uneditedAn issue was discovered in certain Apple products. Safari before 10.1 is affected. The issue involves the "Safari Login AutoFill" component. It allows local users to obtain access to locked keychain items via unspecified vectors.
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 confidenceThis vulnerability in Safari's Login AutoFill component (versions before 10.1) allows a local user to access keychain items that should remain locked. The AutoFill functionality fails to properly protect locked credentials, enabling unauthorized retrieval of stored passwords through unspecified vectors.
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
<= 10.0.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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:L/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Safari versionOn macOS, open Safari > About Safari. On Windows, open Safari > Help > About Safari. Note the full version number (e.g., 10.0.3, 10.1, etc.).Affected if Version is 10.0.3 or earlier (any version below 10.1)
-
Verify AutoFill is enabledOpen Safari > Preferences > AutoFill. Check if any options are checked: 'User names and passwords', 'Credit cards', 'Other forms', or 'Contact info'.Affected if AutoFill is enabled for user names and passwords (this is the attack vector)
-
Confirm Keychain items existOpen Keychain Access app (/Applications/Utilities/Keychain Access.app). Look for 'login' keychain items with passwords stored (items show a password icon or 'password' in the name).Affected if Stored credentials exist in the login keychain that could be AutoFilled
-
Check if keychain is set to lockIn Keychain Access, select the 'login' keychain. Go to Edit > Change Settings for Keychain 'login'. Verify if 'Lock after X minutes of inactivity' is set, or if 'Lock when sleeping' is enabled.Affected if Keychain is set to remain unlocked (no auto-lock configured) - the vulnerability exploits unlocked credentials
You are affected if Safari version is 10.0.3 or earlier AND AutoFill for passwords is enabled with credentials stored in an unlocked keychain.
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 dataUpdate Safari to version 10.1 or later. This is a patch management issue - no code changes or configurations are required; simply deploying the Apple security update resolves the vulnerability.
Fix this in Safari
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-2385 — 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-2017-2385 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