Information Disclosure in Microsoft Windows 10 (CVE-2017-0042)
Summary
Vulnerability in Microsoft Windows 10 (CVE-2017-0042). Risk of unauthorized operations or information disclosure.
Original description
The description as published by the source.
Windows Media Player in Microsoft Windows 8.1; Windows Server 2012 R2; Windows RT 8.1; Windows 7 SP1; Windows 2008 SP2 and R2 SP1, Windows Server 2016; Windows Vista SP2; and Windows 10 Gold, 1511, and 1607 allows remote attackers to obtain sensitive information via a crafted web site, aka "Windows Media Player Information Disclosure Vulnerability."
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2017-0042 has been found in Microsoft Windows 10.
Risk of unauthorized operations or information disclosure. CVSS score: 3.1/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Microsoft Windows 10 CVE-2017-0042" on the vendor's site.
CVE-2017-0042 (Microsoft Windows 10) — CWE-200 / CVSS v3 3.1
Attack vector: remote (network-reachable) / unauthenticated
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Information disclosure (CWE-200) exists in Microsoft Windows 10.
Check the vendor advisory for the affected versions of Microsoft Windows 10.
Severity: Low (CVSS 3.1/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Microsoft Windows 10 を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory securityfocus.com
- patch portal.msrc.microsoft.com
- web pastebin.com
- web securitytracker.com
- web twitter.com