Skip to main content
Mallory
MediumVulnerability

CVE-2017-11927: Microsoft Windows its:// Protocol Handler Information Disclosure

Published Dec 12, 2017 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS6.5Medium · v3
EPSS9.6%96th percentile
CISA KEVNoNot listed
In the wildReported1 exploitation record in Mallory
Vendor
Microsoft Corporation
IdentifiersCVE-2017-11927CWE-200 · Exposure of Sensitive Information…

CVE-2017-11927 is a Microsoft Windows information disclosure vulnerability affecting multiple supported Windows versions. According to the provided description, the flaw exists in the way the Windows its:// protocol handler determines the security zone of a request. Incorrect zone determination can cause content to be treated with less restrictive trust assumptions than intended, enabling disclosure of information. Supporting context indicates Microsoft associated this CVE with fixes for payloads abused through Outlook-rendered HTML content that could trigger outbound requests via URI schemes including its and related handlers, though the core vulnerability description provided here is the Windows its:// protocol handler’s improper zone handling.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can disclose information to an attacker. Based on the supporting context, this included the ability to induce outbound authentication-related requests and potentially expose SMB credential material or otherwise confirm message viewing/tracking in scenarios where the vulnerable handler was reachable through crafted content. The primary documented impact for this CVE is information disclosure rather than direct code execution or privilege escalation.

Mitigation

If you can’t patch tonight, do this now.

Where patching cannot be applied immediately, reduce exposure to attacker-controlled content that can invoke the vulnerable handler. The supporting context recommends operational mitigations relevant to the associated Outlook abuse path, including reading email in plain text, disabling or limiting preview of untrusted email, deleting suspicious messages without opening them, blocking outbound SMB ports 445 and 139, using host firewall controls, and applying Restrict NTLM policies where appropriate. Note that blocking SMB does not necessarily prevent DNS or WebDAV-based tracking behaviors described in the supporting material.

Remediation

Patch, then assume compromise.

Apply the Microsoft security updates associated with CVE-2017-11927. The provided context states the initial fix was released in December 2017 and was updated in May 2018 to address remaining issues referenced in the related research. Systems should be brought fully up to date with the latest cumulative/security updates for the affected Windows versions.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft CorporationWindows 10operating_system
Microsoft CorporationWindows 7operating_system
Microsoft CorporationWindows 8.1operating_system
Microsoft CorporationWindows Rt 8.1operating_system
Microsoft CorporationWindows Serveroperating_system
Microsoft CorporationWindows Server 2008operating_system
Microsoft CorporationWindows Server 2012operating_system
Microsoft CorporationWindows Server 2016operating_system
FAQ

Frequently asked questions

Is CVE-2017-11927 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2017-11927?
As of Oct 16, 2026, Mallory has found no public exploit for CVE-2017-11927.
Is there a patch for CVE-2017-11927?
Apply the Microsoft security updates associated with CVE-2017-11927. The provided context states the initial fix was released in December 2017 and was updated in May 2018 to address remaining issues referenced in the related research.
What products are affected by CVE-2017-11927?
Microsoft Corporation Windows 10, Microsoft Corporation Windows 7, Microsoft Corporation Windows 8.1, Microsoft Corporation Windows Rt 8.1, Microsoft Corporation Windows Server, and 3 more.
How severe is CVE-2017-11927?
CVE-2017-11927 has a CVSS v3 score of 6.5 (Medium) and an EPSS score of 9.6% (96th percentile) as of Oct 16, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.