CVE-2024-6327

9.9 CRITICAL

📋 TL;DR

This CVE describes a remote code execution vulnerability in Progress Telerik Report Server caused by insecure deserialization. Attackers can exploit this to execute arbitrary code on affected systems. Organizations using Telerik Report Server versions before 2024 Q2 (10.1.24.709) are affected.

💻 Affected Systems

Products:
  • Progress Telerik Report Server
Versions: All versions prior to 2024 Q2 (10.1.24.709)
Operating Systems: Windows, Linux
Default Config Vulnerable: ⚠️ Yes
Notes: All default installations are vulnerable. No special configuration required for exploitation.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete system compromise allowing attackers to execute arbitrary code, steal data, install malware, pivot to other systems, and maintain persistent access.

🟠

Likely Case

Attackers gain remote code execution capabilities, potentially leading to data theft, ransomware deployment, or system takeover.

🟢

If Mitigated

With proper network segmentation and access controls, impact limited to isolated reporting systems with minimal data exposure.

🌐 Internet-Facing: HIGH - Internet-facing instances are directly exploitable by remote attackers without authentication.
🏢 Internal Only: HIGH - Internal instances remain vulnerable to insider threats or attackers who breach perimeter defenses.

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: LIKELY
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

Insecure deserialization vulnerabilities are commonly exploited. While no public PoC exists at time of analysis, similar vulnerabilities in Telerik products have been weaponized quickly.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 2024 Q2 (10.1.24.709) or later

Vendor Advisory: https://docs.telerik.com/report-server/knowledge-base/deserialization-vulnerability-cve-2024-6327

Restart Required: Yes

Instructions:

1. Download Telerik Report Server 2024 Q2 (10.1.24.709) or later from vendor portal. 2. Backup current configuration and reports. 3. Install the updated version following vendor documentation. 4. Restart the Report Server service.

🔧 Temporary Workarounds

Network Isolation

all

Restrict network access to Telerik Report Server to only trusted IP addresses and networks.

Use firewall rules to limit inbound connections to specific IP ranges

Application Layer Filtering

all

Implement WAF rules to detect and block deserialization attacks.

Configure WAF to block requests containing serialized objects or suspicious payloads

🧯 If You Can't Patch

  • Isolate the vulnerable system in a separate network segment with strict access controls
  • Implement application-level monitoring and alerting for suspicious deserialization activity

🔍 How to Verify

Check if Vulnerable:

Check the Report Server version in the web interface under Settings > About, or examine the installation directory for version files.

Check Version:

On Windows: Check registry at HKEY_LOCAL_MACHINE\SOFTWARE\Telerik\Report Server\Version. On Linux: Check /opt/telerik/reportserver/version.txt

Verify Fix Applied:

Verify the version is 10.1.24.709 or higher and test that the Report Server functions normally after update.

📡 Detection & Monitoring

Log Indicators:

  • Unusual deserialization errors in application logs
  • Suspicious process creation from Report Server
  • Unexpected network connections from Report Server process

Network Indicators:

  • HTTP requests containing serialized objects to Report Server endpoints
  • Outbound connections from Report Server to unknown external IPs

SIEM Query:

source="telerik-report-server" AND (error="deserialization" OR error="serialization")

🔗 References

📤 Share & Export