CVE-2017-2382
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. macOS Server before 5.3 is affected. The issue involves the "Wiki Server" component. It allows remote attackers to enumerate user accounts 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 · moderate confidenceThis is a user enumeration vulnerability in the Wiki Server component of macOS Server versions prior to 5.3. The vulnerability allows remote unauthenticated attackers to discover valid user account names within the Wiki Server system, potentially aiding subsequent authentication attacks such as password spraying or brute force attempts.
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<= 5.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Determine installed macOS Server versionRun `defaults read /Applications/Server.app/Contents/Info.plist CFBundleShortVersionString` or `system_profiler SPApplicationsDataType | grep -A2 'Server' | head -6`Affected if Version returned is 5.2 or lower (the CVE affects versions prior to 5.3)
-
Confirm Wiki Server service is enabledRun `sudo serveradmin status wiki` to check if the Wiki Server service is currently runningAffected if Service shows as 'RUNNING' or 'enabled' and the version check above shows 5.2 or lower
-
Verify Wiki Server network accessibilityCheck if port 8443 (default Wiki Server port) is listening: `sudo lsof -i :8443 | grep -i wiki` or `netstat -an | grep 8443`Affected if Port 8443 is LISTENING and reachable from network interfaces other than localhost (0.0.0.0 or external IP)
-
Test user enumeration responseSend a crafted request to the Wiki Server login endpoint (e.g., `curl -k https://localhost:8443/wiki/`) and observe whether different error messages are returned for valid vs invalid usernamesAffected if Distinct error messages appear for valid versus invalid usernames, indicating enumeration is possible
Your environment is affected if macOS Server version is 5.2 or earlier AND Wiki Server is enabled and network-accessible, allowing remote attackers to enumerate user accounts through different server responses.
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 macOS Server to version 5.3 or later to remediate this vulnerability. If immediate patching is not feasible, consider restricting network access to the Wiki Server or temporarily disabling it until the update can be applied.
- 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-2017-2382 — 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-2382 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