dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 2 May 2022.
Ui For Asp.net AjaxApplication · Telerik

CVE-2017-11317

CRITICAL · 9.8 CVSS v3.1 Published 2017-08-23
Fix available
A fix is available. Upgrade to after 2016.3.1027 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Telerik.Web.UI in Progress Telerik UI for ASP.NET AJAX before R1 2017 and R2 before R2 2017 SP2 uses weak RadAsyncUpload encryption, which allows remote attackers to perform arbitrary file uploads or execute arbitrary code.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The RadAsyncUpload component in Telerik UI for ASP.NET AJAX uses weak encryption for handling file uploads, allowing remote attackers to bypass the encryption mechanism and upload arbitrary files. This can lead to remote code execution on the affected server.

MitigationUpgrade Telerik UI for ASP.NET AJAX to R1 2017 or later, or R2 2017 SP2 or later. Alternatively, implement additional validation and security controls around the upload functionality.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Ui For Asp.net AjaxApplication
Affected:<= 2016.3.1027= 2017.2.503= 2017.2.621

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Telerik.Web.UI assembly version
    Locate the Telerik.Web.UI.dll file in your application's bin folder. Right-click the DLL, select Properties, and view the Version information. Alternatively, run: [System.Diagnostics.FileVersionInfo]::GetVersionInfo('path\to\Telerik.Web.UI.dll') in PowerShell.
    Affected if The FileVersion or ProductVersion is 2016.3.1027 or earlier, exactly 2017.2.503, or exactly 2017.2.621
  2. Confirm RadAsyncUpload is in use
    Search your application codebase and configuration files for 'RadAsyncUpload' or 'RadUpload' handlers. Check web.config for entries under system.web/httpHandlers or system.webServer/handlers that reference Telerik.AsyncUpload.axd or similar.
    Affected if RadAsyncUpload handler is registered and enabled in the application configuration
  3. Verify encryption key configuration
    Examine the web.config file for appSettings keys: 'Telerik.AsyncUpload.ConfigurationEncryptionKey' and 'Telerik.Upload.ValidationKey'. These should contain strong, unique values, not the default keys known to be publicly available.
    Affected if The encryption keys are missing, left at default values, or are known weak keys (such as 'PrivateKeyForEncryptionOfRadUploadConfiguration')

Your environment is affected if Telerik.Web.UI version falls within the vulnerable ranges AND RadAsyncUpload is enabled, with weak or default encryption keys configured.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 2016.3.1027
Interim mitigation

Upgrade Telerik UI for ASP.NET AJAX to R1 2017 or later, or R2 2017 SP2 or later. Alternatively, implement additional validation and security controls around the upload functionality.

Recommended fix High confidence

Telerik UI for ASP.NET AJAX R2 2017 SP2 (2017.2.711 or later) or the latest R1/R2 release

  1. 1. Identify all instances of Telerik.Web.UI.dll in your project and dependencies
  2. 2. Download the latest version of Telerik UI for ASP.NET AJAX (R2 2017 SP2 or later, or preferably the latest R1/R2 release) from telerik.com
  3. 3. Replace all instances of the vulnerable Telerik.Web.UI.dll with the new version from the download
  4. 4. Rebuild and test your application to ensure all Telerik controls function correctly
  5. 5. Verify that the RadAsyncUpload encryption has been strengthened by reviewing release notes
  6. 6. Deploy the updated application to production
Caveat Review Telerik's release notes for breaking changes between your current version and the target version; major version upgrades may introduce UI/behavioral changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ui For Asp.net Ajax Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,300
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,680.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-11317 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-11317 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data