A Win32k information disclosure vulnerability exists in Microsoft Windows when the win32k component improperly provides kernel information
Published Apr 12, 2017
4.7
MEDIUMCVSS 3.0
EPSS 3.65%
Description
A Win32k information disclosure vulnerability exists in Microsoft Windows when the win32k component improperly provides kernel information. An attacker who successfully exploited the vulnerability could obtain information to further compromise the user's system, aka "Win32k Information Disclosure Vulnerability."
Affected products
-
- Version WindowsStatusaffectedConstraints-
- Version
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Microsoft Corporation | Windows | n/a |
|
- n/a
- 1511
- 1607
- 1703
- n/a
- n/a
- n/a
- n/a
- r2
- n/a
- r2
- n/a
- n/a
No data.
No Red Hat product state for this CVE.
No package ranges for this CVE.
Remediation
No remediation recorded yet.
Metrics
No CVSS v4.0 score for this CVE.
No CVSS v3.1 score for this CVE.
CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
AV:L/AC:M/Au:N/C:P/I:N/A:N
This CVE is not in the KEV list.
No CISA SSVC assessment for this CVE yet.
Estimated probability of exploitation in the wild in the next 30 days (FIRST EPSS). As of Oct 1, 2026.
Score over time
2021–2026- EPSS v1
- EPSS v2
- EPSS v3
- EPSS v4
- EPSS v5
Percentile over time
- EPSS v1
- EPSS v2
- EPSS v3
- EPSS v4
- EPSS v5
Table of values (26 key points)
Flat stretches are collapsed; showing up to 120 newest points.
| Date | Score | Percentile | Model |
|---|---|---|---|
| Oct 1, 2026 | 3.65% (0.03655) | 89.25th | v5 (v2026.06.15) |
| Jun 15, 2026 | 3.65% (0.03655) | 88.13th | v5 (v2026.06.15) |
| Jul 2, 2025 | 16.49% (0.16494) | 94.63th | v4 (v2025.03.14) |
| May 26, 2025 | 17.54% (0.17543) | 94.72th | v4 (v2025.03.14) |
| Mar 30, 2025 | 12.46% (0.12461) | 93.31th | v4 (v2025.03.14) |
| Mar 29, 2025 | 35.94% (0.35936) | 95.52th | v4 (v2025.03.14) |
| Mar 17, 2025 | 12.46% (0.12461) | 93.37th | v4 (v2025.03.14) |
| Dec 12, 2024 | 0.12% (0.00123) | 48.33th | v3 (v2023.03.01) |
| Jul 13, 2024 | 0.14% (0.00137) | 49.63th | v3 (v2023.03.01) |
| Jun 4, 2024 | 0.15% (0.00146) | 50.50th | v3 (v2023.03.01) |
| Apr 24, 2024 | 0.27% (0.00268) | 67.42th | v3 (v2023.03.01) |
| Mar 15, 2024 | 0.22% (0.00220) | 59.22th | v3 (v2023.03.01) |
| Feb 1, 2024 | 0.09% (0.00091) | 38.50th | v3 (v2023.03.01) |
| Dec 24, 2023 | 0.10% (0.00104) | 42.27th | v3 (v2023.03.01) |
| Nov 14, 2023 | 0.11% (0.00111) | 44.16th | v3 (v2023.03.01) |
| Oct 7, 2023 | 0.10% (0.00101) | 41.00th | v3 (v2023.03.01) |
| Aug 28, 2023 | 0.13% (0.00133) | 47.73th | v3 (v2023.03.01) |
| Apr 28, 2023 | 0.13% (0.00127) | 45.95th | v3 (v2023.03.01) |
| Mar 23, 2023 | 0.13% (0.00133) | 46.73th | v3 (v2023.03.01) |
| Mar 7, 2023 | 0.08% (0.00079) | 32.43th | v3 (v2023.03.01) |
| Mar 6, 2023 | 2.19% (0.02185) | 80.92th | v2 (v2022.01.01) |
| Apr 1, 2022 | 2.19% (0.02185) | 79.09th | v2 (v2022.01.01) |
| Feb 4, 2022 | 2.19% (0.02185) | 57.86th | v2 (v2022.01.01) |
| Feb 3, 2022 | 35.03% (0.35026) | 97.90th | v1 |
| Sep 1, 2021 | 35.03% (0.35026) | 98.92th | v1 |
| Apr 14, 2021 | 35.03% (0.35026) | 0.00th | v1 |
References (4)
- http://www.securityfocus.com/bid/97462 vdb-entryx_refsource_BIDThird Party AdvisoryVDB Entry
- http://www.securitytracker.com/id/1038239 vdb-entryx_refsource_SECTRACK
- https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2017-0058 x_refsource_CONFIRMPatchVendor Advisory
- https://www.exploit-db.com/exploits/41879/ exploitx_refsource_EXPLOIT-DB
| Link | Providers | Tags |
|---|---|---|
| http://www.securityfocus.com/bid/97462 | vdb-entryx_refsource_BIDThird Party AdvisoryVDB Entry | |
| http://www.securitytracker.com/id/1038239 | vdb-entryx_refsource_SECTRACK | |
| https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2017-0058 | x_refsource_CONFIRMPatchVendor Advisory | |
| https://www.exploit-db.com/exploits/41879/ | exploitx_refsource_EXPLOIT-DB |
Change history (0)
No recorded changes yet.