CVE-2017-8613

CVE-2017-8613 is a high-severity vulnerability in Microsoft Azure Active Directory Connect with a CVSS 3.x base score of 8.1. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-640.

Key facts

Description

Azure AD Connect Password writeback, if misconfigured during enablement, allows an attacker to reset passwords and gain unauthorized access to arbitrary on-premises AD privileged user accounts aka "Azure AD Connect Elevation of Privilege Vulnerability."

Frequently asked questions

What is CVE-2017-8613?
Azure AD Connect Password writeback, if misconfigured during enablement, allows an attacker to reset passwords and gain unauthorized access to arbitrary on-premises AD privileged user accounts aka "Azure AD Connect Elevation of Privilege Vulnerability."
How severe is CVE-2017-8613?
CVE-2017-8613 has a CVSS 3.x base score of 8.1, rated high severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2017-8613 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 4% (88th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2017-8613?
CVE-2017-8613 affects Microsoft Azure Active Directory Connect. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2017-8613?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2017-8613 published?
CVE-2017-8613 was published on 2017-06-29 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Microsoft Azure Active Directory Connect

All CVEs affecting Microsoft Azure Active Directory Connect →

Other CWE-640 vulnerabilities

Browse all CWE-640 vulnerabilities →