Threats / Telerik / CVE-2017-11357
CVE-2017-11357
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Telerik User Interface (UI) for ASP.NET AJAX vulnerability
Telerik UI for ASP.NET AJAX contains an insecure direct object reference vulnerability in RadAsyncUpload allowing file uploads to restricted locations and remote code execution.
Verdict
Today item, not a backlog item.
An unauthenticated attacker can exploit improper input validation in RadAsyncUpload to bypass access controls, upload malicious files to arbitrary server locations, and achieve remote code execution on affected systems.
CISA KEV Yes · 2023-01-264Ransomware use Flagged4EPSS 0.75709 (verify live)5Exploit Weaponized · public PoC6CVSS 9.8 (CISA)3CISA SSVC Exploitation: active · Automatable: yes · Impact: total3
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
5 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2023-01-26), flagged for known ransomware use.
Probability (EPSS)
EPSS 0.75709 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) · Affected: Telerik, User Interface (UI) for ASP.NET AJAX. Confirm exact fixed builds in the vendor advisory.CVSS — CISA-assigned via the ADP container (CVE.org), version 3.1; the CNA left no metrics, so CISA's own score is used ahead of NVD.
Weakness (CWE)
Mapped to CWE-20 Improper Input Validation.CWE assignment from the public NVD record (may be stale); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 1982 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I bypass access controls through direct object reference manipulation in the RadAsyncUpload component.
Business
Attackers gain unauthorized file upload capability without proper authentication or authorization checks.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I upload executable files to restricted directories on the web server.
Business
Malicious code is placed in locations where it can be executed by the application or web server process.
3
Lateral reach — past segmentation narrative 3
Attacker
I trigger execution of the uploaded files to achieve remote code execution on the server.
Business
The attacker gains full control of the affected server and can deploy ransomware or establish persistent access.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05