Forum

The forum is a free service supported by community members. Please consider opening a support ticket if you need timely help.

PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 18 May 2020 06:27 PM by  Walter Boyd
Telerik?
 2 Replies
Sort:
You are not authorized to post a reply.
Author Messages


New Member


Posts:36
New Member


--
12 May 2020 11:42 PM

    My site is failing PCI Compliance tests because it has links to jQuery v1.9.1. And after upgrading or removing every possible old jQuery*.js file, I figured out that this script is hard-coded in the Telerik.UI dll. So, I'm trying to remove Telerik dependency, but this seems to break my store:
    Unable to create type 'dnn2:DnnComboBox'. Could not load file or assembly 'Telerik.Web.UI,

    Do you have a version that is not dependent on Telerik controls?

    Thanks!

    0


    Veteran Member


    Posts:2956
    Veteran Member


    --
    13 May 2020 08:30 PM

    Hi Walter,

    We are still in the process of removing all dependencies on Telerik. We've removed a lot already, but unfortunately, this could take several more months to complete. If you're using one of the latest Storefront (e.g. v15.12+ or v16) all the public facing pages including all Manage modules do not have any dependencies on Telerik anymore (for display templates, make sure to use the razor template. That means don't use any "StandardXX" where the XX is a Number as those are the old Web forms templates with Telerik dependencies). That leaves only some internal Admin pages using Telerik and that's going away too as we refactor those out.

    Furthermore, in your Web.config, you should be able remove most Telerik handler bindings all except this one below. Remove any reference to Telerik Chart, Upload, etc. (especially Upload, which is the one mentioned in the last security vulnerability).

    <add name="Telerik.Web.UI.WebResource" verb="*" path="Telerik.Web.UI.WebResource.axd" type="Telerik.Web.UI.WebResource, Telerik.Web.UI" preCondition="integratedMode" />

    I'm not sure how your scanner works, if it picks up only the external public facing pages. If so, then I think this might be sufficient to minimize exposure.

    0


    New Member


    Posts:36
    New Member


    --
    18 May 2020 06:27 PM

    FYI, I was able to get past this issue by using IIS to block the specific querystring that retrieved the old jquery.

    0
    You are not authorized to post a reply.