Menu

Star on GitHub · 3.2k

CVE-2016-3258

4.7 · MEDIUM

Race condition in the kernel in Microsoft Windows 8.1, Windows Server 2012 Gold and R2, Windows RT 8.1, and Windows 10 Gold and 1511 allows local users to bypass the Low Integrity protection mechan…

Published Jul 13, 2016CWE-264EPSS 0.93%

Overview

CVE-2016-3258 is a medium-severity vulnerability. It was published on July 13, 2016 and has a CVSS 3.0 base score of 4.7 (MEDIUM).

This vulnerability has a CVSS 3.0 base score of 4.7, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

Race condition in the kernel in Microsoft Windows 8.1, Windows Server 2012 Gold and R2, Windows RT 8.1, and Windows 10 Gold and 1511 allows local users to bypass the Low Integrity protection mechanism and write to files by leveraging unspecified object-manager features, aka "Windows File System Security Feature Bypass."

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2016-3258?

CVE-2016-3258 is a medium-severity vulnerability. It was published on July 13, 2016 and has a CVSS 3.0 base score of 4.7 (MEDIUM).

How severe is CVE-2016-3258?

This vulnerability has a CVSS 3.0 base score of 4.7, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2016-3258?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2016-3258?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2016-3258 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related MEDIUM CVEs from 2016

View all