CVE-2019-18935: Progress Telerik UI for ASP.NET AJAX Deserialization of Untrusted Data
Progress Telerik UI for ASP.NET AJAX · listed in the CISA catalog of actively exploited vulnerabilities since 2021-11-03.
- CVSS v3.1 (CISA ADP)
- 9.8
- critical
- EPSS (exploit probability, 30 days)
- 99.7%
- among the highest 0.1% of all CVEs
- Added to CISA KEV
- 2021-11-03
- US federal due date 2022-05-03
- Automatable (CISA SSVC)
- yes
- technical impact: total
CVE-2019-18935 explained
CVE-2019-18935 is a .NET deserialization vulnerability in the RadAsyncUpload function of Progress Telerik UI for ASP.NET AJAX through 2019.3.1023. When the encryption keys are known, an unauthenticated attacker can achieve remote code execution. CISA lists it as known exploited, including in ransomware campaigns.
Impact
An attacker who knows the encryption keys, for example through CVE-2017-11317 or CVE-2017-11357, can execute code remotely on the server. The attack works over the network with low complexity and needs no privileges or user interaction. CISA rates it automatable with total technical impact, meaning full control of the affected component. Confidentiality, integrity and availability are all highly affected. Attackers are known to exploit it, including for ransomware.
Who is affected
The description names Progress Telerik UI for ASP.NET AJAX through 2019.3.1023. The CVE record itself lists no affected versions and names no fixed version. According to the description, from 2020.1.114 a default setting prevents the exploit. In 2019.3.1023, but not earlier versions, a non-default setting can prevent exploitation. Check the vendor advisory for exact fixed releases.
Written with AI from the data on this page and checked against it automatically.
Official description
Progress Telerik UI for ASP.NET AJAX through 2019.3.1023 contains a .NET deserialization vulnerability in the RadAsyncUpload function. This is exploitable when the encryption keys are known due to the presence of CVE-2017-11317 or CVE-2017-11357, or other means.
Exploitation can result in remote code execution. (As of 2020.1.114, a default setting prevents the exploit. In 2019.3.1023, but not earlier versions, a non-default setting can prevent exploitation.)
CISA required action: Apply updates per vendor instructions.
CISA notes
How to fix it
- The CVE record names no fixed version – check the vendor advisory and CISA's required action for updates and mitigations.
- Vendor advisory: telerik.com/support/whats-new/release-history
- CISA's deadline for US federal agencies: 2022-05-03 (passed) – a useful benchmark for everyone else, too.
What to do
- Update Progress Telerik UI for ASP.NET AJAX per vendor instructions; the description states
2020.1.114and later prevent the exploit by default. - If you run
2019.3.1023and cannot upgrade immediately, enable the non-default setting that prevents exploitation, as described in the vendor advisory. - Remediate CVE-2017-11317 and CVE-2017-11357, which can expose the encryption keys this attack needs.
- Inventory all applications that bundle Telerik UI for ASP.NET AJAX, including third-party and legacy web apps.
- Check exposed servers for signs of compromise, given known exploitation and ransomware use.
The CVE record names no fixed version. Follow CISA's required action: apply updates per vendor instructions. The description states that from 2020.1.114 a default setting prevents the exploit, and in 2019.3.1023 a non-default setting can prevent it. Consult the vendor advisory for the exact upgrade path and configuration, and restrict exposure of affected applications until remediated.
Written with AI from the data on this page and checked against it automatically.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- Yes – attackers can automate it at scale
- Technical impact
- Total – full control of the component or total information disclosure
Weakness: CWE-502 Deserialization of Untrusted Data
Questions about CVE-2019-18935
- Is CVE-2019-18935 being exploited?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2021-11-03 and notes known ransomware use. The US federal due date was 2022-05-03.
- Does an attacker need credentials?
- No. No privileges or user interaction are required. However, exploitation depends on the encryption keys being known, for example through CVE-2017-11317, CVE-2017-11357 or other means.
- Which version prevents the exploit by default?
- According to the description, as of
2020.1.114a default setting prevents the exploit. Version2019.3.1023can be protected with a non-default setting; earlier versions cannot.
Written with AI from the data on this page and checked against it automatically.
References
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-22. Always confirm with the vendor's or distribution's advisory before patching.