What is CVE-2017-0022?A medium-severity flaw criminals are using now.

Medium severityKnown exploited11 affected products
The short answer

CVE-2017-0022 is a medium-severity flaw (CVSS 6.5) in XML Core Services from Microsoft, published on 17 March 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 18%. If you run an affected version, patch it first.

Published 17 March 2017. Record last updated 20 April 2025. We keep this page's data up to date.

What it does

What is CVE-2017-0022? In plain terms.

It can be attacked from anywhere on the internet without logging in, but a person has to take an action first. If it works, the attacker can read data.

The official description

Microsoft XML Core Services (MSXML) in Windows 10 Gold, 1511, and 1607; Windows 7 SP1; Windows 8.1; Windows RT 8.1; Windows Server 2008 SP2 and R2 SP1; Windows Server 2012 Gold and R2; Windows Server 2016; and Windows Vista SP2 improperly handles objects in memory, allowing attackers to test for files on disk via a crafted web site, aka "Microsoft XML Information Disclosure Vulnerability."

What kind of flaw is it?

  • CWE-119Improper Restriction of Operations within the Bounds of a Memory Buffer
CVSS 3.1 scoreMedium · 6.5

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 clickYes, a person has to take an action
  • What an attacker getsCan read data

Severity vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

Exploitation

Is CVE-2017-0022 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 18%.

Known to be exploitedYesOn the government list of exploited flaws
Chance of use in the next 30 days18%Its EPSS score, from the latest forecast

Timeline

  1. Published
  2. Record last updated
  3. Exploit likelihood jumped
  4. Exploit likelihood fell
How Precursor Intelligence ranks it
72out of 100High

CVE-2017-0022 scores 72. 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-0022 matches software you track, it lands in your list with its score and the reasons behind it.

See your own ranked list →
Affected products

Who is affected by CVE-2017-0022? 11 products.

The published record lists 11 products from 1 vendor. If you run one of these, check your version, then go to the fix below.

Remediation

How do I fix CVE-2017-0022? Four steps.

  1. 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.
  2. Apply the vendor’s fixInstall the update named in the vendor’s advisory. We’ve put the advisory first in the list.
  3. 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.
  4. 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.

References

4 links
Precursor Intelligence

Does CVE-2017-0022 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.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. 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.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

CVE-2017-0022 is a medium-severity flaw in XML Core Services from Microsoft, published on 17 March 2017. It can be attacked from anywhere on the internet without logging in, but a person has to take an action first. If it works, the attacker can read data.

It scores 6.5 out of 10 on the CVSS severity scale, which is medium. Our risk score for CVE-2017-0022 is 72 out of 100, which is High. 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 18%.

For XML Core Services from Microsoft: 3.0. The record lists 11 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.