dbcve.org
Telerik Ui For Asp.net AjaxApplication · Progress

CVE-2019-19790

CRITICAL · 9.8 CVSS v3.1 Published 2019-12-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
Path traversal in RadChart in Telerik UI for ASP.NET AJAX allows a remote attacker to read and delete an image with extension .BMP, .EXIF, .GIF, .ICON, .JPEG, .PNG, .TIFF, or .WMF on the server through a specially crafted request. NOTE: RadChart was discontinued in 2014 in favor of RadHtmlChart. All RadChart versions were affected. To avoid this vulnerability, you must remove RadChart's HTTP handler from a web.config (its type is Telerik.Web.UI.ChartHttpHandler).

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

Path traversal vulnerability in Telerik UI for ASP.NET AJAX's discontinued RadChart component allows remote attackers to read or delete image files with extensions .BMP, .EXIF, .GIF, .ICON, .JPEG, .PNG, .TIFF, or .WMF on the server via specially crafted requests.

MitigationRemove the Telerik.Web.UI.ChartHttpHandler registration from web.config to eliminate the vulnerable RadChart HTTP handler. Since RadChart was discontinued in 2014, this handler should not be in use.

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
Telerik Ui For Asp.net AjaxApplication
Affected:all versions
RadchartApplication
Affected:all versions

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. Locate Telerik.Web.UI.dll in the application
    Search the application bin directory for Telerik.Web.UI.dll, or inspect the compiled assemblies if source is unavailable
    Affected if The Telerik UI for ASP.NET AJAX library is present in the application
  2. Identify if RadChart is in use
    Search project files for references to RadChart, Telerik.Web.UI.RadChart, or TelerikChart declarations in .aspx, .ascx, or code-behind files
    Affected if The application uses or references the RadChart component
  3. Check web.config for ChartHttpHandler registration
    Open web.config and search for 'Telerik.Web.UI.ChartHttpHandler' within the <httpHandlers> section
    Affected if The ChartHttpHandler is registered in web.config
  4. Verify handler is enabled for the application
    Confirm the handler is not commented out or removed; check for any corresponding entries in <handlers> section for IIS integrated mode
    Affected if The ChartHttpHandler is active and not disabled

The environment is affected if Telerik UI for ASP.NET AJAX with RadChart is present and the Telerik.Web.UI.ChartHttpHandler is registered and enabled in web.config, allowing specially crafted requests to read or delete image files via path traversal.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Remove the Telerik.Web.UI.ChartHttpHandler registration from web.config to eliminate the vulnerable RadChart HTTP handler. Since RadChart was discontinued in 2014, this handler should not be in use.

Recommended fix High confidence
  1. Locate the web.config file in the ASP.NET application root directory
  2. Search the web.config file for entries containing 'Telerik.Web.UI.ChartHttpHandler' or the RadChart HTTP handler registration
  3. Remove the entire <add> or <remove> element that registers the Telerik.Web.UI.ChartHttpHandler handler (typically found in the <httpHandlers> section under <system.web> and/or <system.webServer> handlers section)
  4. Save the updated web.config file
  5. Test the application to ensure it functions correctly without RadChart
  6. If charting functionality is still required, migrate to RadHtmlChart (the successor to RadChart, discontinued in 2014)
Caveat RadChart functionality will no longer be available; if charting is still needed, migration to RadHtmlChart is required (this may require code changes as the APIs differ)

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

Fix this in Telerik Ui For Asp.net Ajax Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-19790 — 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-2019-19790 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