Skip to main content

CVE-2025-47996: CWE-191: Integer Underflow (Wrap or Wraparound) in Microsoft Windows 10 Version 1809

High
VulnerabilityCVE-2025-47996cvecve-2025-47996cwe-191cwe-125
Published: Tue Jul 08 2025 (07/08/2025, 16:57:32 UTC)
Source: CVE Database V5
Vendor/Project: Microsoft
Product: Windows 10 Version 1809

Description

Integer underflow (wrap or wraparound) in Windows MBT Transport driver allows an authorized attacker to elevate privileges locally.

AI-Powered Analysis

AILast updated: 08/07/2025, 00:48:54 UTC

Technical Analysis

CVE-2025-47996 is a high-severity integer underflow vulnerability (CWE-191) found in the Microsoft Windows 10 Version 1809 MBT Transport driver. This vulnerability arises due to an integer underflow condition, where arithmetic operations cause the integer value to wrap around, leading to unexpected behavior. Specifically, the flaw exists in the MBT Transport driver component, which is part of the Windows networking stack. An authorized attacker with local access and low privileges can exploit this vulnerability to escalate their privileges to SYSTEM level, thereby gaining full control over the affected system. The vulnerability does not require user interaction but does require the attacker to have some level of local access (local privilege). The CVSS v3.1 base score is 7.8, indicating a high severity with high impact on confidentiality, integrity, and availability. The vulnerability was reserved in May 2025 and published in July 2025, with no known exploits in the wild at the time of publication. No official patches or mitigation links have been provided yet, which suggests that affected organizations need to be vigilant and consider interim mitigations. The flaw is specific to Windows 10 Version 1809 (build 10.0.17763.0), which is an older version of Windows 10, and may still be in use in some environments, especially in legacy or industrial systems.

Potential Impact

For European organizations, the impact of this vulnerability can be significant, especially in environments where Windows 10 Version 1809 is still deployed. Successful exploitation allows an attacker with local access to escalate privileges to SYSTEM level, potentially leading to full system compromise. This could enable attackers to bypass security controls, access sensitive data, install persistent malware, or disrupt critical services. Sectors such as finance, healthcare, manufacturing, and government agencies that rely on legacy Windows 10 systems could face increased risk. The vulnerability's ability to compromise confidentiality, integrity, and availability simultaneously makes it particularly dangerous. Moreover, the lack of user interaction requirement facilitates automated or scripted exploitation once local access is obtained. Although no known exploits are currently in the wild, the high severity and ease of exploitation (low complexity, no UI required) mean that attackers may develop exploits rapidly. This risk is exacerbated in environments with weak local access controls or where endpoint security solutions do not adequately monitor or restrict driver-level operations.

Mitigation Recommendations

Given the absence of official patches, European organizations should prioritize the following mitigations: 1) Upgrade or migrate systems from Windows 10 Version 1809 to a supported, patched version of Windows 10 or Windows 11 to eliminate exposure. 2) Restrict local access to systems by enforcing strict access control policies, including limiting administrative privileges and using least privilege principles. 3) Employ application whitelisting and endpoint detection and response (EDR) solutions to monitor and block suspicious driver-level activities or privilege escalation attempts. 4) Harden systems by disabling or restricting the MBT Transport driver if it is not required for business operations, through device or driver management policies. 5) Conduct regular audits of local user accounts and remove or disable unnecessary accounts to reduce the attack surface. 6) Monitor system and security logs for unusual activities indicative of privilege escalation attempts. 7) Prepare incident response plans specifically addressing local privilege escalation scenarios to enable rapid containment and remediation. These targeted mitigations go beyond generic advice by focusing on controlling local access, driver management, and proactive monitoring tailored to this vulnerability's characteristics.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
microsoft
Date Reserved
2025-05-14T14:44:20.085Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 686d50d46f40f0eb72f91b39

Added to database: 7/8/2025, 5:09:40 PM

Last enriched: 8/7/2025, 12:48:54 AM

Last updated: 8/12/2025, 12:33:54 AM

Views: 11

Actions

PRO

Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats