CVE-2020-11414
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 · uneditedAn issue was discovered in Progress Telerik UI for Silverlight before 2020.1.330. The RadUploadHandler class in RadUpload for Silverlight expects a web request that provides the file location of the uploading file along with a few other parameters. The uploading file location should be inside the directory where the upload handler class is defined. Before 2020.1.330, a crafted web request could result in uploads to arbitrary locations.
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 confidenceThe RadUploadHandler class in Telerik UI for Silverlight RadUpload component before version 2020.1.330 does not properly validate the file location parameter in incoming web requests, allowing path traversal that enables attackers to upload files to arbitrary locations on the server rather than only within the designated upload directory.
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< 2020.1.330CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Identify Telerik UI for Silverlight installationSearch for Telerik.Silverlight.dll or Telerik.Web.UI.dll assemblies in the application bin folder or GAC, and note the file version propertyAffected if The assembly exists and its version is below 2020.1.330
-
Confirm RadUpload component is in useSearch project files and referenced assemblies for RadUpload, RadUploadHandler, or Telerik.Windows.Controls.RadUploadAffected if The RadUpload component is referenced or used in the application code
-
Check for RadUploadHandler ashx handlerLook for .ashx files or web.config handler registrations that reference RadUploadHandler or Telerik.Web.UI.RadUploadHandlerAffected if A handler mapping for RadUploadHandler exists in the web application
-
Verify upload directory configurationExamine the web.config or application settings for RadUploadTargetFolder or similar upload path configurationAffected if An upload directory is configured and the RadUploadHandler is accessible via web requests
-
Compare installed version to vulnerable rangeUse the file properties of the Telerik assembly to determine the exact version number, then compare to 2020.1.330Affected if The installed version is any release prior to 2020.1.330
The environment is affected if Telerik UI for Silverlight with the RadUpload component is installed at a version below 2020.1.330 and the RadUploadHandler is accessible via web requests.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor data2020.1.330
Upgrade Telerik UI for Silverlight to version 2020.1.330 or later which includes proper path validation to restrict uploads to the intended directory.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-11414 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-11414 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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