{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-23315 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-23315 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-23315 is a high-severity denial of service vulnerability in Microsoft Chakracore, published on 20 Jan 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-23315 and fix it if it is affected.\n\nWhat it is: CVE-2020-23315 is a high-severity denial of service vulnerability in Microsoft Chakracore, published on 20 Jan 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-23315 in the wild and no public exploit code.\n\nAffected product: Microsoft Chakracore. 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-2020-23315/ (Markdown: https://insights.sbomify.com/CVE-2020-23315/index.md)","id":"CVE-2020-23315","markdown":"https://insights.sbomify.com/CVE-2020-23315/index.md","name":"CVE-2020-23315","record":{"aliases":["GHSA-2hmc-2j98-55mm"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"ChakraCore JavaScript engine","requires_auth":"none","summary":"An assertion failure in ChakraCore's debug context allows attackers to cause a denial of service via crafted JavaScript.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"chakracore","vendor":"microsoft"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[],"description":"There is an ASSERTION (pFuncBody-\u003eGetYieldRegister() == oldYieldRegister) failed in Js::DebugContext::RundownSourcesAndReparse in ChakraCore version 1.12.0.0-beta.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Denial of service in n/a","id":"CVE-2020-23315","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"microsoft:chakracore","products":["microsoft:chakracore"],"type":"denial_of_service","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Denial of service in n/a","id":"CVE-2020-23319"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2020-23314"},"products":["n/a"],"published":"2022-01-20","related":[{"cvss_score":7.5,"headline":"ChakraCore Scripting Engine Type Confusion","id":"CVE-2018-8298","kev_date_added":"2022-03-03","published":"2018-07-11"},{"cvss_score":4.2,"headline":"Microsoft Edge and Internet Explorer Memory Corruption","id":"CVE-2020-0878","kev_date_added":"2021-11-03","published":"2020-09-11"},{"cvss_score":9.8,"headline":"ChakraCore RCE Vulnerability","id":"CVE-2018-8500","kev_date_added":null,"published":"2018-10-10"},{"cvss_score":9.8,"headline":"ChakraCore vulnerable to privilege escalation","id":"CVE-2017-11767","kev_date_added":null,"published":"2017-11-02"},{"cvss_score":9.8,"headline":"ChakraCore RCE Vulnerability","id":"CVE-2017-8658","kev_date_added":null,"published":"2017-08-11"},{"cvss_score":8.8,"headline":"Scripting Engine Memory Corruption Vulnerability","id":"CVE-2020-1555","kev_date_added":null,"published":"2020-08-17"},{"cvss_score":8.1,"headline":"ChakraCore RCE Vulnerability","id":"CVE-2020-1073","kev_date_added":null,"published":"2020-06-09"}],"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":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"An assertion failure in ChakraCore's debug context allows attackers to cause a denial of service via crafted JavaScript.","url":"https://insights.sbomify.com/CVE-2020-23315/"}