{"answers":{"affected":"2 open source packages ship an affected version, including angular-expressions. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-5219 in the wild and no public exploit code.","fix":"Upgrade angular-expressions to 1.0.1 or later.","what":"CVE-2020-5219 is a high-severity code injection vulnerability in peerigon angular-expressions, published on 24 Jan 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2020-5219 and fix it if it is affected.\n\nWhat it is: CVE-2020-5219 is a high-severity code injection vulnerability in peerigon angular-expressions, published on 24 Jan 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2020-5219 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- angular-expressions (npm): affected all versions; fixed in 1.0.1\n- angular-expressions (npm): affected all versions; fixed in 1.0.1\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-5219/ (Markdown: https://insights.sbomify.com/CVE-2020-5219/index.md)","id":"CVE-2020-5219","markdown":"https://insights.sbomify.com/CVE-2020-5219/index.md","name":"CVE-2020-5219","record":{"aliases":["GHSA-hxhm-96pp-2m43"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Angular expressions library","requires_auth":"low_privilege","summary":"Attackers can execute arbitrary code by passing user-controlled input to the compile function in the Angular Expressions library.","user_interaction":"required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"angular-expressions","vendor":"peerigon"}],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-74","name":"Improper Neutralization of Special Elements in Output Used by a Downstream Component"}],"description":"Angular Expressions before version 1.0.1 has a remote code execution vulnerability if you call expressions.compile(userControlledInput) where userControlledInput is text that comes from user input. If running angular-expressions in the browser, an attacker could run any browser script when the application code calls expressions.compile(userControlledInput). If running angular-expressions on the server, an attacker could run any Javascript expression, thus gaining Remote Code Execution.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Remote Code Execution in Angular Expressions","id":"CVE-2020-5219","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"code_injection","year":"2020"},"n_packages":2,"n_references":3,"next":{"headline":"Ability to expose data in Sylius by using an unintended serialisation group","id":"CVE-2020-5220"},"packages":[{"ecosystem":"npm","fixed":["1.0.1"],"introduced":["0"],"last_affected":[],"package":"angular-expressions","purl":null,"source":"GHSA-hxhm-96pp-2m43"},{"ecosystem":"npm","fixed":["1.0.1"],"introduced":["0"],"last_affected":[],"package":"angular-expressions","purl":"pkg:npm/angular-expressions","source":"GHSA-hxhm-96pp-2m43"}],"prev":{"headline":"Ability in Sylius to switch channels via GET parameter enabled in production environments","id":"CVE-2020-5218"},"products":["angular-expressions"],"published":"2020-01-24","related":[{"cvss_score":9.3,"headline":"Angular Expressions - Remote Code Execution using filters","id":"CVE-2026-44643","kev_date_added":null,"published":"2026-05-11"},{"cvss_score":8.5,"headline":"Angular Expressions - Remote Code Execution","id":"CVE-2021-21277","kev_date_added":null,"published":"2021-02-01"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["peerigon"]},"summary":"Attackers can execute arbitrary code by passing user-controlled input to the compile function in the Angular Expressions library.","url":"https://insights.sbomify.com/CVE-2020-5219/"}