CVE-2017-15887
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 improper restriction of excessive authentication attempts vulnerability in /principals in Synology CardDAV Server before 6.0.7-0085 allows remote attackers to obtain user credentials via a brute-force attack.
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 confidenceSynology CardDAV Server versions prior to 6.0.7-0085 fail to implement proper rate limiting or account lockout mechanisms on the /principals authentication endpoint, allowing remote attackers to perform unlimited credential brute-force attempts until valid user credentials are obtained.
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< 6.0.7-0085CVSS 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
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 if Synology CardDAV Server is installedLog into Synology DiskStation Manager (DSM) and navigate to Package Center to check if the CardDAV Server package is installed. Alternatively, check for running processes or services related to CardDAV on the system.Affected if CardDAV Server package is not installed on the Synology NAS - the system is not affected.
-
Check the installed CardDAV Server versionIn DSM Package Center, click on CardDAV Server and view the version information. Alternatively, use the command line to query the package version if available (e.g., via synopkg or similar package management tools on Synology).Affected if The installed version is prior to 6.0.7-0085 - the vulnerability is present.
-
Verify if the /principals endpoint is accessibleFrom an external or internal client, attempt to access the CardDAV Server /principals endpoint (typically at a URL path like /principals/ or /carddav/principals/) using a web browser or curl command. Check if the endpoint responds to unauthenticated or authenticated requests.Affected if The /principals endpoint is reachable from a network where attackers could attempt brute-force attacks - exposure risk exists.
-
Confirm lack of rate limiting or account lockoutTest the authentication mechanism by making multiple failed login attempts to the CardDAV Server. Observe whether any rate limiting (delays, CAPTCHAs) or account lockout (account disabled after N failed attempts) occurs. Document the behavior.Affected if Multiple failed authentication attempts proceed without any enforced delays, CAPTCHA challenges, or account lockout - the vulnerability is exploitable.
A Synology NAS with CardDAV Server installed at a version prior to 6.0.7-0085 and with the /principals endpoint exposed to untrusted networks is affected by this lack of rate limiting, allowing credential brute-force attacks.
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.
dbcve · scoped6.0.7-0085
Upgrade Synology CardDAV Server to version 6.0.7-0085 or later to receive the vendor fix. As interim measures, consider network-level rate limiting, Web Application Firewall rules, or restricting external access to the CardDAV server.
CardDAV Server 6.0.7-0085 or later
- Access Synology DiskStation Manager (DSM) as administrator
- Open Package Center and locate CardDAV Server
- Check current installed version of CardDAV Server (should be below 6.0.7-0085)
- In Package Center, click Update to install the latest available version of CardDAV Server
- Alternatively, manually download the update from Synology's download center and install via Manual Install in Package Center
- Verify the updated version is 6.0.7-0085 or later
- Confirm the /principals endpoint now enforces proper rate limiting on authentication attempts
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-15887 — 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-15887 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