{"answers":{"affected":"It affects 1 product.","exploited":"Yes. Attackers have exploited CVE-2017-11357 in the wild since at least 26 Jan 2023, including in ransomware campaigns.","fix":"No fix has been published for CVE-2017-11357 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 16 Feb 2023.","what":"CVE-2017-11357 is a critical vulnerability in n/a, published on 23 Aug 2017. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-11357 and fix it if it is affected.\n\nWhat it is: CVE-2017-11357 is a critical vulnerability in n/a, published on 23 Aug 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: Yes. Attackers have exploited CVE-2017-11357 in the wild since at least 26 Jan 2023, including in ransomware campaigns.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2017-11357/ (Markdown: https://insights.sbomify.com/CVE-2017-11357/index.md)","id":"CVE-2017-11357","markdown":"https://insights.sbomify.com/CVE-2017-11357/index.md","name":"CVE-2017-11357","record":{"aliases":["GHSA-52hx-8455-4qwv"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"ASP.NET AJAX UI library","requires_auth":"none","summary":"Remote attackers can upload arbitrary files and execute code via the RadAsyncUpload control in Progress Telerik UI for ASP.NET AJAX.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"telerik_ui_for_asp.net_ajax","vendor":"progress"}],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-434","name":"Unrestricted Upload of File with Dangerous Type"}],"description":"Progress Telerik UI for ASP.NET AJAX before R2 2017 SP2 does not properly restrict user input to RadAsyncUpload, which allows remote attackers to perform arbitrary file uploads or execute arbitrary code.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2018-01-24","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2018-01-24","kind":"exploitdb","ref":"43874","stars":null,"title":"Telerik UI for ASP.NET AJAX 2012.3.1308 \u003c 2017.1.118 - Arbitrary File Upload"}],"tier":"exploited"},"has_fix":null,"headline":"Telerik UI for ASP.NET AJAX Insecure Direct Object Reference","id":"CVE-2017-11357","indexable":true,"kev":{"dateAdded":"2023-01-26","dueDate":"2023-02-16","knownRansomwareCampaignUse":"Known","product":"User Interface (UI) for ASP.NET AJAX","requiredAction":"Apply updates per vendor instructions.","vendorProject":"Telerik","vulnerabilityName":"Telerik UI for ASP.NET AJAX Insecure Direct Object Reference Vulnerability"},"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"file_upload","year":"2017"},"n_packages":0,"n_references":2,"next":{"headline":"Denial of service in n/a","id":"CVE-2017-11358"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2017-11356"},"products":["n/a"],"published":"2017-08-23","related":[{"cvss_score":9.8,"headline":"Missing authorization in n/a","id":"CVE-2021-28141","kev_date_added":null,"published":"2021-03-11"},{"cvss_score":9.8,"headline":"Path traversal in n/a","id":"CVE-2019-19790","kev_date_added":null,"published":"2019-12-13"},{"cvss_score":8.1,"headline":"RadAsyncUpload AsyncUploadTypeName Type Resolution Vulnerability in Telerik UI for ASP.NET AJAX","id":"CVE-2026-13181","kev_date_added":null,"published":"2026-07-22"},{"cvss_score":8.1,"headline":"PersistenceFramework Cookie Deserialization Vulnerability in Telerik UI for ASP.NET AJAX","id":"CVE-2026-13185","kev_date_added":null,"published":"2026-07-22"},{"cvss_score":8.1,"headline":"AppDataStorageProvider Path Traversal Deserialization Vulnerability in Telerik UI for ASP.NET AJAX","id":"CVE-2026-13186","kev_date_added":null,"published":"2026-07-22"},{"cvss_score":8.1,"headline":"DialogHandler Provider Type Tampering Vulnerability in Telerik UI for ASP.NET AJAX","id":"CVE-2026-13187","kev_date_added":null,"published":"2026-07-22"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"open","licence":"CC0 1.0","name":"CISA KEV"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":"yes","exploitation":"active","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-08-14","vendors":["n/a"]},"summary":"Remote attackers can upload arbitrary files and execute code via the RadAsyncUpload control in Progress Telerik UI for ASP.NET AJAX.","url":"https://insights.sbomify.com/CVE-2017-11357/"}