How severe is CVE-2017-11357?

CVE-2017-11357 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which products are affected by CVE-2017-11357?

Affected package information for CVE-2017-11357 is not yet fully mapped. Check the official advisory links for details.

How do I patch CVE-2017-11357?

Apply the progress telerik ui for asp.net ajax security patch or hotfix for CVE-2017-11357 on the affected version, following the vendor advisory for your exact build.

How do I detect CVE-2017-11357 across my infrastructure?

Inventory every progress telerik ui for asp.net ajax deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for remote code execution at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.

How do I mitigate CVE-2017-11357 if there is no patch (or I can't update yet)?

Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.

How does O3 Security protect against CVE-2017-11357?

O3 detects and blocks CVE-2017-11357 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Is CVE-2017-11357 actively exploited in the wild?

Yes. There are 3 known exploit references for CVE-2017-11357, including 1 documented proof-of-concept exploit on Exploit-DB and 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2017-11357?

CVE-2017-11357 has an EPSS (Exploit Prediction Scoring System) score of 75.7%, placing it in the 99th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is CVE-2017-11357 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2017-11357 (Telerik UI for ASP.NET AJAX Insecure Direct Object Reference Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2023-01-26. CISA required all US federal civilian agencies to remediate this vulnerability by 2023-02-16. The required action was: Apply updates per vendor instructions. This CVE has been used in known ransomware campaigns. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2017-11357?

CVE-2017-11357 is classified as Unrestricted File Upload (CWE-434). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Which products and versions are affected by CVE-2017-11357?

CVE-2017-11357 affects progress telerik ui for asp.net ajax. Check the affected-products list on this page against your deployed version to confirm exposure.

When was CVE-2017-11357 published, and has it been updated?

CVE-2017-11357 was published on August 23, 2017 and was last updated on June 17, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV·Added 2023-01-26 — agencies required to remediate by 2023-02-16 · Ransomware

CVE-2017-11357

CRITICAL

Progress Telerik UI for ASP.NET AJAX before R2 2017 SP2 does not properly restrict user input to RadAsyncUpload, which allows remote attackers to perform arbitrary file uploads or execute…

Published

Aug 23, 2017

Updated

Jun 17, 2026

Affected

0 pkgs

Patched

None yet

Exploits

3 known

EPSS Exploitation Probability

via FIRST.org ↗

75.7%probability of exploitation in next 30 days

Very High Risk99th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

Progress Telerik UI for ASP.NET AJAX before R2 2017 SP2 does not properly restrict user input to RadAsyncUpload, which allows remote attackers to perform arbitrary file uploads or execute arbitrary code.

Affected Products

1 product · 1 configurations

Application

telerik ui for asp.net ajaxprogress

< 2020.1.114

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-43874webappsaspx

Telerik UI for ASP.NET AJAX 2012.3.1308 < 2017.1.118 - Arbitrary File Upload

by Paul Taylor · Jan 24, 2018

Exploit-DB Source

Detection & mitigation playbook

Vendor / appliance

Detect
Inventory every progress telerik ui for asp.net ajax deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for remote code execution at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.
Fix
Apply the progress telerik ui for asp.net ajax security patch or hotfix for CVE-2017-11357 on the affected version, following the vendor advisory for your exact build.
Workarounds
Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.
How O3 protects you
O3 detects and blocks CVE-2017-11357 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Tailored to CVE-2017-11357. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Runtime Protection

Is CVE-2017-11357 being exploited in your environment?

O3's eBPF runtime sensors and L7 egress monitoring detect and block the CVE-2017-11357 exploit chain at execution — protecting unpatched and end-of-life systems until the vendor patch is applied.

Protect my workloads How runtime protection works