Progress UI for WinForms Dekomprimierungspfad-Traversal-Schwachstelle

The core of this vulnerability lies in the improper limitation of a target path when decompressing archives within Telerik UI for WinForms. An attacker could craft a malicious archive designed to exploit this weakness. By manipulating the path, they can force the application to extract files into directories where it shouldn't have write access. This could allow them to overwrite critical system files, inject malicious code, or gain control of the affected system. The potential impact extends beyond simple file access; successful exploitation could lead to complete system compromise, data exfiltration, and denial of service.

Applications utilizing Telerik UI for WinForms to process user-uploaded files or handle external data streams are particularly at risk. Legacy applications using older versions of the framework and those with inadequate input validation routines are also more vulnerable. Shared hosting environments where multiple applications share the same file system could experience broader impact if one application is compromised.

• dotnet / windows: Use Process Monitor to observe file system activity when Telerik UI for WinForms is processing archives. Look for attempts to extract files into unexpected or restricted directories.

Get-Process | Where-Object {$_.ProcessName -like '*Telerik*'} | Get-Process -IncludeChildren

• dotnet / windows: Examine application event logs for errors related to file extraction or access denied errors when attempting to write to restricted directories. • dotnet / windows: Review Telerik UI for WinForms configuration files for any custom settings related to archive processing or file system paths. Look for any misconfigurations that could contribute to the vulnerability.

1. 2025-02-12Disclosure

   disclosure

1. Reserviert2025-01-08
2. Veröffentlicht2025-02-12
3. EPSS aktualisiert2026-04-02

The primary mitigation for CVE-2025-0332 is to upgrade to Telerik UI for WinForms version 2025.1.211 or later. If immediate upgrading is not feasible, consider implementing stricter file system permissions to limit write access to sensitive directories. Additionally, input validation and sanitization should be implemented to prevent attackers from manipulating the target path. While a WAF is unlikely to directly mitigate this vulnerability, it could potentially block malicious archive uploads. After upgrading, verify the fix by attempting to decompress a specially crafted archive with a manipulated path and confirming that the extraction fails with an appropriate error.