SafariWeb browser · Apple
CVE-2011-0160
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 · uneditedWebKit, as used in Apple Safari before 5.0.4 and iOS before 4.3, does not properly handle redirects in conjunction with HTTP Basic Authentication, which might allow remote web servers to capture credentials by logging the Authorization HTTP header.
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 confidenceWebKit browser engine does not clear HTTP Basic Authentication credentials (Authorization header) when processing redirect responses, causing browsers to send authentication credentials to redirect target servers that may be controlled by attackers.
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
<= 5.0.3= 1.0= 1.0.0= 1.0.0b1= 1.0.0b2= 1.0.1= 1.0.2= 1.0.3= 1.1= 1.1.0= 1.1.1= 1.2all versions<= 4.2= 1.0.0= 1.0.1= 1.0.2= 1.1.0= 1.1.1= 1.1.2= 1.1.3= 1.1.4= 1.1.5= 2.0= 2.0.0CVSS 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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/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.
-
Identify the browser engine in useCheck if the browser is WebKit-based (Safari, any WebKit-derived browser) or if the application uses the WebKit rendering engineAffected if The browser or application uses WebKit as its rendering engine
-
Check Safari browser versionIn Safari, go to Safari menu > About Safari to view the version numberAffected if Safari version is 5.0.3 or earlier, or matches any of the specific affected versions listed (1.0 through 1.2, 5.0 through 5.0.3)
-
Check WebKit engine versionIn Safari, visit any webpage and view the User-Agent string, or check the application's internal version information if using a WebKit-based applicationAffected if Any WebKit version is installed, as the vulnerability affects all versions of Apple WebKit
-
Check iOS version on iPhone/iPadOn the iOS device, go to Settings > General > About and note the version numberAffected if iOS version is 4.2 or earlier, or matches any of the specific affected versions listed (1.0.0 through 2.0.0)
-
Confirm redirect handling behaviorThis requires testing: attempt a network redirect from a site requiring Basic Auth and observe if the Authorization header is sent to the redirect target. Use developer tools or a proxy to inspect HTTP headersAffected if The Authorization header (containing Base64-encoded credentials) is present in the request to the redirect target server, rather than being cleared
You are affected if you are using Safari 5.0.3 or earlier, any version of Apple WebKit, or iOS 4.2 or earlier, and the browser sends HTTP Basic Authentication credentials to redirect target servers.
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 affected Apple products (Safari to 5.0.4+, iOS to 4.3+) to obtain the patched WebKit version. No configuration-based workarounds exist for this client-side 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-2011-0160 — 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-2011-0160 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