CVE-2024-10012

7.8 HIGH

📋 TL;DR

This vulnerability allows remote code execution through insecure deserialization in Progress Telerik UI for WPF. Attackers can exploit this to execute arbitrary code on affected systems. Organizations using vulnerable versions of Telerik UI for WPF are affected.

💻 Affected Systems

Products:
  • Progress Telerik UI for WPF
Versions: All versions prior to 2024 Q4 (2024.4.1111)
Operating Systems: Windows
Default Config Vulnerable: ⚠️ Yes
Notes: Any application built with vulnerable Telerik UI for WPF components is affected regardless of how the application is deployed.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Full system compromise with attacker gaining complete control over the affected system, potentially leading to data theft, ransomware deployment, or lateral movement within the network.

🟠

Likely Case

Remote code execution allowing attackers to install malware, create backdoors, or exfiltrate sensitive data from vulnerable applications.

🟢

If Mitigated

Limited impact with proper network segmentation, application hardening, and monitoring detecting exploitation attempts before successful compromise.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ⚠️ Yes
Complexity: MEDIUM

Insecure deserialization vulnerabilities are commonly exploited and weaponization is likely given the high impact.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 2024 Q4 (2024.4.1111) or later

Vendor Advisory: https://docs.telerik.com/devtools/wpf/knowledge-base/kb-security-unsafe-deserialization-cve-2024-10012

Restart Required: Yes

Instructions:

1. Update Telerik UI for WPF to version 2024.4.1111 or later. 2. Rebuild and redeploy any applications using the vulnerable components. 3. Restart affected services and applications.

🔧 Temporary Workarounds

Application Hardening

all

Implement input validation and sanitization for all deserialization operations

Network Segmentation

all

Isolate vulnerable applications from critical systems and internet exposure

🧯 If You Can't Patch

  • Implement strict network access controls to limit exposure of vulnerable applications
  • Deploy runtime application self-protection (RASP) or web application firewall (WAF) with deserialization attack detection

🔍 How to Verify

Check if Vulnerable:

Check the Telerik UI for WPF version in your application's dependencies or assembly information. Versions below 2024.4.1111 are vulnerable.

Check Version:

Check assembly version in .NET applications or review package dependencies in project files.

Verify Fix Applied:

Verify the Telerik UI for WPF version is 2024.4.1111 or higher after patching and rebuilding applications.

📡 Detection & Monitoring

Log Indicators:

  • Unusual process creation from WPF applications
  • Deserialization errors or exceptions in application logs
  • Suspicious network connections from WPF applications

Network Indicators:

  • Malformed serialized data payloads to WPF application endpoints
  • Unexpected outbound connections from WPF applications

SIEM Query:

Process Creation where Parent Process contains 'wpf' OR Application Logs containing 'deserialization' AND 'exception'

🔗 References

📤 Share & Export