CVE-2019-18935
Telerik UI for ASP.NET AJAX vulnerability analysis and mitigation

Overview

Progress Telerik UI for ASP.NET AJAX through 2019.3.1023 contains a .NET deserialization vulnerability (CVE-2019-18935) in the RadAsyncUpload function. The vulnerability allows remote code execution when encryption keys are known due to the presence of CVE-2017-11317 or CVE-2017-11357. As of version 2020.1.114, a default setting prevents the exploit, while in version 2019.3.1023 a non-default setting can prevent exploitation (NVD, Bishop Fox).

Technical details

The vulnerability exists in the RadAsyncUpload handler's processing of the rauPostData parameter in file upload requests. The parameter contains both a serialized configuration object and the object's type. When deserializing, the handler uses JavaScriptSerializer.Deserialize() method which calls setter methods for the specified object type. If an attacker controls this type parameter, they can specify a gadget class that enables remote code execution during deserialization. The exploit typically involves first using CVE-2017-11317 to upload a malicious mixed mode assembly DLL, then exploiting CVE-2019-18935 to load and execute that DLL (Bishop Fox, Code White).

Impact

Successful exploitation can result in remote code execution on the underlying host in the context of the w3wp.exe process. Attackers can execute arbitrary commands, deploy additional payloads, establish persistence, and potentially gain complete control of the affected system (Telerik KB).

Exploitability

The vulnerability has been actively exploited in the wild. In March 2023, attackers successfully compromised a U.S. federal agency by exploiting this vulnerability to deploy malicious payloads and exfiltrate data. Multiple threat actors, including an APT actor and the cybercriminal group XE Group, have been observed exploiting this vulnerability (Bleeping Computer).

Mitigation and workarounds

Organizations should upgrade to Telerik UI for ASP.NET AJAX version R1 2020 (2020.1.114) or later, where the AllowedCustomMetaDataTypes security feature is enabled by default. For version 2019.3.1023, organizations should explicitly enable the AllowedCustomMetaDataTypes security setting. Additionally, organizations should ensure proper configuration of encryption keys and implement recommended security settings as detailed in Telerik's RadAsyncUpload security guide (Telerik KB).

Additional resources


SourceThis report was generated using AI

Related Telerik UI for ASP.NET AJAX vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2026-6023CRITICAL9.8
  • Telerik UI for ASP.NET AJAX logoTelerik UI for ASP.NET AJAX
  • cpe:2.3:a:telerik:ui_for_asp.net_ajax
NoYesApr 22, 2026
CVE-2021-28141CRITICAL9.8
  • Telerik UI for ASP.NET AJAX logoTelerik UI for ASP.NET AJAX
  • cpe:2.3:a:telerik:ui_for_asp.net_ajax
NoYesMar 11, 2021
CVE-2019-18935CRITICAL9.8
  • Telerik UI for ASP.NET AJAX logoTelerik UI for ASP.NET AJAX
  • cpe:2.3:a:telerik:ui_for_asp.net_ajax
YesYesDec 11, 2019
CVE-2017-11357CRITICAL9.8
  • Telerik UI for ASP.NET AJAX logoTelerik UI for ASP.NET AJAX
  • cpe:2.3:a:telerik:ui_for_asp.net_ajax
YesYesAug 23, 2017
CVE-2025-3600HIGH7.5
  • Telerik UI for ASP.NET AJAX logoTelerik UI for ASP.NET AJAX
  • cpe:2.3:a:telerik:ui_for_asp.net_ajax
NoYesMay 14, 2025

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management