CVE-2015-8570
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 password reset functionality in Lepide Active Directory Self Service allows remote authenticated users to change arbitrary domain user passwords via a crafted request.
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 is an authorization bypass vulnerability in Lepide Active Directory Self Service's password reset function. An authenticated user with normal privileges can send a crafted request to reset the password of any domain user account, including privileged accounts like Domain Admins, due to missing or insufficient authorization checks in the password reset endpoint.
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 dataall versionsCVSS 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
- Adjacent
- Complexity
- M
- Authentication
- Single
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:A/AC:M/Au:S/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.
-
Confirm Lepide AD Self Service is installedIdentify whether Lepide Active Directory Self Service is present in your environment. Check installed programs or application inventory for this product.Affected if Lepide Active Directory Self Service is installed and running
-
Verify password reset endpoint is accessibleCheck if the password reset web portal or API endpoint is exposed and accessible to authenticated users. Review web application access controls and URL paths.Affected if The password reset functionality is enabled and reachable by standard authenticated users
-
Review user role assignments for password reset privilegesExamine the role-based access control (RBAC) configuration within Lepide AD Self Service to determine which user roles can reset passwords. Check if normal/unprivileged users have password reset capabilities.Affected if Standard authenticated users (non-administrators) have the ability to initiate password resets for any user account
-
Test password reset for privileged accountsUsing a normal-privilege test account, attempt to reset the password of a privileged account (such as Domain Admin) through the Lepide self-service portal. Verify if the request is accepted without proper authorization validation.Affected if A normal user can successfully reset passwords for privileged domain accounts without elevated permissions
If Lepide Active Directory Self Service is installed and standard users can reset passwords for privileged accounts, the environment is affected by CVE-2015-8570.
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 dataApply the vendor-supplied patch for CVE-2015-8570 to Lepide Active Directory Self Service immediately. Additionally, review and enforce role-based access controls to ensure only designated administrators can reset passwords for privileged accounts.
- 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-2015-8570 — 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-2015-8570 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