{"answers":{"affected":"It affects 1 product.","exploited":"Yes. Attackers have exploited CVE-2019-18935 in the wild since at least 3 Nov 2021, including in ransomware campaigns.","fix":"No fix has been published for CVE-2019-18935 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 3 May 2022.","what":"CVE-2019-18935 is a critical unsafe deserialization vulnerability in n/a, published on 11 Dec 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-18935 and fix it if it is affected.\n\nWhat it is: CVE-2019-18935 is a critical unsafe deserialization vulnerability in n/a, published on 11 Dec 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: Yes. Attackers have exploited CVE-2019-18935 in the wild since at least 3 Nov 2021, 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-2019-18935/ (Markdown: https://insights.sbomify.com/CVE-2019-18935/index.md)","id":"CVE-2019-18935","markdown":"https://insights.sbomify.com/CVE-2019-18935/index.md","name":"CVE-2019-18935","record":{"aliases":["GHSA-c655-3j45-33xw"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"ASP.NET AJAX UI library","requires_auth":"none","summary":"Attackers can achieve remote code execution via unsafe deserialization in RadAsyncUpload if encryption keys are known or default settings are not enforced.","user_interaction":"not_required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"ui_for_asp.net_ajax","vendor":"telerik"}],"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-502","name":"Deserialization of Untrusted Data"}],"description":"Progress Telerik UI for ASP.NET AJAX through 2019.3.1023 contains a .NET deserialization vulnerability in the RadAsyncUpload function. This is exploitable when the encryption keys are known due to the presence of CVE-2017-11317 or CVE-2017-11357, or other means. Exploitation can result in remote code execution. (As of 2020.1.114, a default setting prevents the exploit. In 2019.3.1023, but not earlier versions, a non-default setting can prevent exploitation.)","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2018-01-09","github_poc":17,"max_poc_stars":373,"metasploit":1,"nuclei":0,"refs":[{"date":"2019-12-12T07:58:11Z","kind":"github_poc","ref":"https://github.com/noperator/CVE-2019-18935","stars":373,"title":"RCE exploit for a .NET JSON deserialization vulnerability in Telerik UI for ASP.NET AJAX."},{"date":"2018-01-09T13:53:57Z","kind":"github_poc","ref":"https://github.com/bao7uo/RAU_crypto","stars":179,"title":"Telerik UI for ASP.NET AJAX File upload and .NET deserialisation exploit (CVE-2017-11317, CVE-2017-11357, CVE-2019-18935)"},{"date":"2020-08-19T17:11:02Z","kind":"github_poc","ref":"https://github.com/murataydemir/CVE-2019-18935","stars":16,"title":"[CVE-2019-18935] Telerik UI for ASP.NET AJAX (RadAsyncUpload Handler) .NET JSON Deserialization"},{"date":"2023-12-25T06:45:11Z","kind":"github_poc","ref":"https://github.com/dust-life/CVE-2019-18935-memShell","stars":13,"title":null},{"date":"2020-05-25T08:37:51Z","kind":"github_poc","ref":"https://github.com/ThanHuuTuan/Telerik_CVE-2019-18935","stars":12,"title":"TelerikUI Vulnerability Scanner (CVE-2019-18935)"},{"date":"2025-07-09T16:41:18Z","kind":"github_poc","ref":"https://github.com/ekkoo-z/CVE-2019-18935-bypasswaf","stars":8,"title":null},{"date":"2020-09-30T10:00:16Z","kind":"github_poc","ref":"https://github.com/random-robbie/CVE-2019-18935","stars":5,"title":"CVE-2019-18935"},{"date":"2020-05-29T07:29:52Z","kind":"github_poc","ref":"https://github.com/ThanHuuTuan/CVE_2019_18935","stars":2,"title":"This project for CVE-2019-18935"}],"tier":"exploited"},"has_fix":null,"headline":"Progress Telerik UI for ASP.NET AJAX Deserialization of Untrusted Data","id":"CVE-2019-18935","indexable":true,"kev":{"dateAdded":"2021-11-03","dueDate":"2022-05-03","knownRansomwareCampaignUse":"Known","product":"Telerik UI for ASP.NET AJAX","requiredAction":"Apply updates per vendor instructions.","vendorProject":"Progress","vulnerabilityName":"Progress Telerik UI for ASP.NET AJAX Deserialization of Untrusted Data Vulnerability"},"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"deserialization","year":"2019"},"n_packages":0,"n_references":10,"next":{"headline":"Denial of service in n/a","id":"CVE-2019-18936"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-2019-18934"},"products":["n/a"],"published":"2019-12-11","related":[{"cvss_score":9.8,"headline":"Telerik UI for ASP.NET AJAX Unrestricted File Upload","id":"CVE-2017-11317","kev_date_added":"2022-04-11","published":"2017-08-23"}],"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":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"yes","exploitation":"active","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-10-21","vendors":["n/a"]},"summary":"Attackers can achieve remote code execution via unsafe deserialization in RadAsyncUpload if encryption keys are known or default settings are not enforced.","url":"https://insights.sbomify.com/CVE-2019-18935/"}