CVE-2015-1674

CVE-2015-1674 is a medium-severity vulnerability in Microsoft Windows 8 with a CVSS 2.0 base score of 4.6. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-254.

Key facts

Description

The kernel in Microsoft Windows 8, Windows 8.1, Windows Server 2012 Gold and R2, and Windows RT Gold and 8.1 does not properly validate an unspecified address, which allows local users to bypass the KASLR protection mechanism, and consequently discover the cng.sys base address, via a crafted application, aka "Windows Kernel Security Feature Bypass Vulnerability."

Frequently asked questions

What is CVE-2015-1674?
The kernel in Microsoft Windows 8, Windows 8.1, Windows Server 2012 Gold and R2, and Windows RT Gold and 8.1 does not properly validate an unspecified address, which allows local users to bypass the KASLR protection mechanism, and consequently discover the cng.sys base address, via a crafted application, aka "Windows Kernel Security Feature Bypass Vulnerability."
How severe is CVE-2015-1674?
CVE-2015-1674 has a CVSS 2.0 base score of 4.6, rated medium severity.
Is CVE-2015-1674 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 3% (87th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2015-1674?
CVE-2015-1674 primarily affects Microsoft Windows 8. In total, 6 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2015-1674?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2015-1674 published?
CVE-2015-1674 was published on 2015-05-13 and last updated on 2026-06-17.

References

Affected products (6)

More vulnerabilities in Microsoft Windows 8

All CVEs affecting Microsoft Windows 8 →

Other CWE-254 vulnerabilities

Browse all CWE-254 vulnerabilities →