CVE-2011-3213
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 · uneditedThe File Systems component in Apple Mac OS X before 10.7.2 does not properly track the specific X.509 certificate that a user manually accepted for an initial https WebDAV connection, which allows man-in-the-middle attackers to hijack WebDAV communication by presenting an arbitrary certificate for a subsequent connection.
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 confidenceMac OS X before 10.7.2 has a certificate tracking flaw in its WebDAV client. When a user manually accepts an X.509 certificate for the initial HTTPS WebDAV connection, the system fails to remember and validate the specific certificate presented. Subsequent connections accept any certificate for that server, allowing man-in-the-middle attackers to intercept WebDAV traffic by presenting their own certificate.
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<= 10.7.1= 10.0= 10.0.0= 10.0.1= 10.0.2= 10.0.3= 10.0.4= 10.1= 10.1.0= 10.1.1= 10.1.2= 10.1.3<= 10.7.1= 10.0= 10.0.0= 10.0.1= 10.0.2= 10.0.3= 10.0.4= 10.1= 10.1.0= 10.1.1= 10.1.2= 10.1.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
- Network
- Complexity
- High
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:H/Au:N/C:C/I:C/A:C
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 Mac OS X versionOpen Apple menu > About This Mac, or run 'sw_vers' in Terminal. Look for the version number (e.g., 10.7.1, 10.6.8, etc.)Affected if Version is 10.7.1 or earlier (including 10.0.x through 10.1.x series)
-
Confirm WebDAV client usageIdentify if any applications or system features are connecting to WebDAV servers over HTTPS. Check for mounted WebDAV volumes in Finder, or review network connections using 'lsof' or 'netstat' for port 443 connections to known WebDAV servers.Affected if The system actively uses HTTPS WebDAV connections
-
Determine if certificate acceptance occurredReview whether any HTTPS WebDAV connections have been established where the user manually accepted a certificate prompt. Check application logs or user history for WebDAV mount operations.Affected if A WebDAV connection was made where the user manually accepted a server certificate
-
Assess MITM exposureVerify if WebDAV traffic could be intercepted by checking network path integrity or whether the WebDAV server certificate has changed since initial acceptance.Affected if Network path to WebDAV server is untrusted or certificate has changed since initial acceptance
The environment is affected if Mac OS X version is 10.7.1 or earlier AND HTTPS WebDAV connections are in use where a certificate was manually accepted, allowing any certificate to be accepted for subsequent connections.
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 dataUpgrade Mac OS X to version 10.7.2 or later, which implements proper certificate pinning for WebDAV connections.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-3213 — 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-3213 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