Vulnerability

CVE-2017-0022

Medium· 6.5KEVCVSS6.5EPSS37%

.rules3/5

Microsoft XML Core Services Information Disclosure Vulnerability

Microsoft XML Core Services (MSXML) improperly handles objects in memory, allowing attackers to test for files on disk via a crafted web site.

Threat signal

81/100

High

Severity

medium

CVSS

6.5

EPSS

37%

Active

KEV

CISA KEV — actively exploited

1460d overdue

AffectedMicrosoft — XML Core Services

Added to KEV

2022-05-24

Federal patch due (BOD 22-01)

2022-06-14

Required action (CISA verbatim)

Apply updates per vendor instructions.

Vendor advisory + references

https://nvd.nist.gov/vuln/detail/CVE-2017-0022

CISA description: “Microsoft XML Core Services (MSXML) improperly handles objects in memory, allowing attackers to test for files on disk via a crafted web site.”

CVSS

v3.1Open in FIRST calculator →

6.5/ 10MEDIUMCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

Attack VectorNetworkExploitable remotely over the internet — no local access needed.
Attack ComplexityLowNo special conditions — exploit works reliably.
Privileges RequiredNoneUnauthenticated — no credentials needed.
User InteractionRequiredRequires user action (click, file open, etc).
ScopeUnchangedImpact contained to the vulnerable component.
Confidentiality ImpactHighTotal disclosure of sensitive data.
Integrity ImpactNoneNo integrity impact.
Availability ImpactNoneNo availability impact.

EPSS

Exploit prediction · 30-day horizonFIRST.org →

36.7%

probability of exploitation in next 30 days

p97

higher than 97% of all CVEs

3-day trend↑ 0pp

Above the FIRST 'patch on a priority schedule' threshold.

Vendor VEX

No VEX statements published for CVE-2017-0022. Vendors publish VEX (Vulnerability Exploitability eXchange) to assert per-product whether a CVE is actually exploitable in their distribution.

SSVCAttend

Active exploitation with limited impact — coordinate patching

exploitation: active
automatable: no
impact: partial
mission: support

Lifecycle

2022-05-24Added to CISA KEVransomware: Unknown
2022-05-24Published
2022-06-14Federal patch due (BOD 22-01)
2026-06-12Last modified1 source

No source-event history recorded yet. New revisions will appear here as ingestors re-fetch this CVE.