Microsoft Windows 7/8 NULL Pointer win32k.sys IsHandleEntrySecure memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.0 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in Microsoft Windows 7/8. Impacted is the function IsHandleEntrySecure of the file win32k.sys of the component NULL Pointer Handler. The manipulation leads to memory corruption.
Furthermore, an exploit is available.
It is suggested to upgrade the affected component.
Details
A vulnerability, which was classified as problematic, has been found in Microsoft Windows 7/8 (Operating System). This issue affects the function IsHandleEntrySecure of the file win32k.sys of the component NULL Pointer Handler. The manipulation with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. Impacted is availability.
The weakness was published 11/12/2013 by sixtyvividtails as win32 handle validation local dos as not defined posting (Pastebin). The advisory is shared at pastebin.com. The exploitation is known to be difficult. An attack has to be approached locally. A simple authentication is needed for exploitation. Technical details as well as a public exploit are known.
After immediately, there has been an exploit disclosed. The exploit is available at pastebin.com. It is declared as proof-of-concept. We expect the 0-day to have been worth approximately $100k and more.
Upgrading eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at OSVDB (99881†). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
License
Support
- end of life (old version)
Website
- Vendor: https://www.microsoft.com/
- Product: https://www.microsoft.com/en-us/windows
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.0
VulDB Base Score: 5.5
VulDB Temp Score: 5.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Exploit Delay Time: 🔍
Timeline
11/12/2013 🔍11/12/2013 🔍
11/21/2013 🔍
09/17/2018 🔍
Sources
Vendor: microsoft.comProduct: microsoft.com
Advisory: win32 handle validation local dos
Researcher: sixtyvividtails
Status: Not defined
GCVE (VulDB): GCVE-100-11225
OSVDB: 99881
scip Labs: https://www.scip.ch/en/?labs.20140213
Entry
Created: 11/21/2013 14:33Updated: 09/17/2018 07:06
Changes: 11/21/2013 14:33 (47), 09/17/2018 07:06 (2)
Complete: 🔍
Committer: olku
Cache ID: 216:F4B:103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.