Microsoft Windows up to Server 2025 MapUrlToZone resolution of path

Summaryinfo

A vulnerability was found in Microsoft Windows. It has been classified as problematic. This issue affects some unknown processing of the component MapUrlToZone. Performing a manipulation results in resolution of path. This vulnerability is known as CVE-2025-21247. Remote exploitation of the attack is possible. No exploit is available. Applying a patch is the recommended action to fix this issue.

Detailsinfo

A vulnerability, which was classified as problematic, was found in Microsoft Windows. This affects an unknown code block of the component MapUrlToZone. The manipulation with an unknown input leads to a resolution of path vulnerability. CWE is classifying the issue as CWE-41. The product is vulnerable to file system contents disclosure through path equivalence. Path equivalence involves the use of special characters in file and directory names. The associated manipulations are intended to generate multiple names for the same object. This is going to have an impact on confidentiality. The summary by CVE is:

Improper resolution of path equivalence in Windows MapUrlToZone allows an unauthorized attacker to bypass a security feature over a network.

The weakness was published 03/11/2025 as confirmed security update guide (Website). The advisory is shared at msrc.microsoft.com. This vulnerability is uniquely identified as CVE-2025-21247. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 07/03/2025). MITRE ATT&CK project uses the attack technique T1006 for this issue.

It is declared as proof-of-concept.

Applying a patch is able to eliminate this problem. A possible mitigation has been published immediately after the disclosure of the vulnerability.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Operating System

Vendor

• Microsoft

Name

• Windows

Version

• 10
• 10 21H2
• 10 22H2
• 10 1607
• 10 1809
• 11 22H2
• 11 23H2
• 11 24H2
• Server 2008 R2 SP1
• Server 2008 SP2
• Server 2012
• Server 2012 R2
• Server 2016
• Server 2019
• Server 2022
• Server 2022 23H2
• Server 2025

License

• commercial

Website

• Vendor: https://www.microsoft.com/
• Product: https://www.microsoft.com/en-us/windows

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion