What is CVE-2017-8543?A critical-severity flaw criminals are using now.
CVE-2017-8543 is a critical-severity flaw (CVSS 9.8) in Windows Server 2008 from Microsoft, published on 15 June 2017. It is on the list of flaws known to be exploited, so criminals are already using it. The latest forecast puts its chance of use in the next 30 days at 74%. If you run an affected version, patch it first.
Published 15 June 2017. Record last updated 20 April 2025. We keep this page's data up to date.
What is CVE-2017-8543? In plain terms.
It can be attacked from anywhere on the internet without logging in, and nobody has to click anything. If it works, the attacker can read data, change data and take it offline.
Microsoft Windows XP SP3, Windows XP x64 XP2, Windows Server 2003 SP2, Windows Vista, Windows 7 SP1, Windows Server 2008 SP2 and R2 SP1, Windows 8, Windows 8.1 and Windows RT 8.1, Windows Server 2012 and R2, Windows 10 Gold, 1511, 1607, and 1703, and Windows Server 2016 allow an attacker to take control of the affected system when Windows Search fails to handle objects in memory, aka "Windows Search Remote Code Execution Vulnerability".
What kind of flaw is it?
- CWE-281Improper Preservation of Permissions
How an attack on it works
Read straight from its severity rating, translated out of the shorthand.
- Where an attacker can beAnywhere on the internet
- How hard it is to pull offEasy: no special conditions
- Login needed firstNo login needed
- Does someone have to clickNo, nobody has to do anything
- What an attacker getsCan read data, change data and take it offline
Severity vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Is CVE-2017-8543 being exploited? Yes.
Attackers are already using it. It is on the government list of flaws known to be exploited, and the latest forecast puts the chance of it being used in the next 30 days at 74%.
Timeline
- Published
- Record last updated
- Exploit likelihood fell
CVE-2017-8543 scores 90. Action: Emergency patch.
We keep the score of every published flaw up to date as the evidence changes. Four things go into the score, and evidence that criminals are actually using it counts most. In order:
- Evidence it is being exploitedBiggest factor
- How severe it isStrong factor
- How widely exposed it isSmaller factor
- Threat activity around itSmaller factor
85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score.
When CVE-2017-8543 matches software you track, it lands in your list with its score and the reasons behind it.
See your own ranked list →Who is affected by CVE-2017-8543? 10 products.
The published record lists 10 products from 1 vendor. If you run one of these, check your version, then go to the fix below.
- Operating system
Windows Server 2008
by Microsoft
Affected versionsr2-sp1 - Operating system
Windows 10 1507
by Microsoft
Affected versionsversion not specified - Operating system
Windows 10 1511
by Microsoft
Affected versionsversion not specified - Operating system
Windows 10 1607
by Microsoft
Affected versionsversion not specified - Operating system
Windows 10 1703
by Microsoft
Affected versionsversion not specified - Operating system
Windows 7
by Microsoft
Affected versionsversion not specified - Operating system
Windows 8.1
by Microsoft
Affected versionsversion not specified - Operating system
Windows Rt 8.1
by Microsoft
Affected versionsversion not specified - Operating system
Windows Server 2012
by Microsoft
Affected versionsr2
How do I fix CVE-2017-8543? Four steps.
- Check whether you run itCompare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list.
- Apply the vendor’s fixInstall the update named in the vendor’s advisory. We’ve put the advisory first in the list.
- If you can’t patch todayFollow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
- Check it wasn’t used before you patchedBecause criminals are already using this flaw, look for signs of a break-in on affected systems using the vendor’s guidance.
Does CVE-2017-8543 affect you? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 flaw being exploited affects software Acme tracks
Microsoft Windows XP SP3, Windows XP x64 XP2, Windows Server 2003 SP2, Windows Vista, Windows 7 SP1, Windows Server 2008 SP2 and R2 SP1, Windows 8, Windows 8...
- Matched to
- Windows Server 2008 on Acme's software list
- What to do
- Patch first, then check for signs of use
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
CVE-2017-8543 is a critical-severity flaw in Windows Server 2008 from Microsoft, published on 15 June 2017. It can be attacked from anywhere on the internet without logging in, and nobody has to click anything. If it works, the attacker can read data, change data and take it offline.
It scores 9.8 out of 10 on the CVSS severity scale, which is critical. Our risk score for CVE-2017-8543 is 90 out of 100, which is Critical. Its action is "Emergency patch". Attackers are using this flaw today. If you run an affected version, it goes to the top of your list.
Attackers are already using it. It is on the government list of flaws known to be exploited, and the latest forecast puts the chance of it being used in the next 30 days at 74%.
For Windows Server 2008 from Microsoft: r2-sp1. The record lists 10 products in all, each with its versions, under "Who is affected" on this page.
Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet. Because criminals are already using it, also check affected systems for signs of a break-in.