{"id":"EUVD-2021-0555","enisaUuid":"48d795f5-a91b-3fca-86f5-972d9fe721dc","description":"angular-expressions is \"angular\u0027s nicest part extracted as a standalone module for the browser and node\". In angular-expressions before version 1.1.2 there is a vulnerability which allows Remote Code Execution if you call \"expressions.compile(userControlledInput)\" where \"userControlledInput\" is text that comes from user input. The security of the package could be bypassed by using a more complex payload, using a \".constructor.constructor\" technique. In terms of impact: 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. This is fixed in version 1.1.2 of angular-expressions A temporary workaround might be either to disable user-controlled input that will be fed into angular-expressions in your application or allow only following characters in the userControlledInput.","datePublished":"Feb 1, 2021, 3:05:24 PM","dateUpdated":"Aug 3, 2024, 6:09:15 PM","baseScore":8.5,"baseScoreVersion":"3.1","baseScoreVector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:N","references":"https://github.com/peerigon/angular-expressions/security/advisories/GHSA-j6px-jwvv-vpwq\nhttps://www.npmjs.com/package/angular-expressions\nhttp://blog.angularjs.org/2016/09/angular-16-expression-sandbox-removal.html\nhttps://github.com/peerigon/angular-expressions/commit/07edb62902b1f6127b3dcc013da61c6316dd0bf1\n","aliases":"CVE-2021-21277\nGHSA-j6px-jwvv-vpwq\n","assigner":"GitHub_M","epss":2.85,"enisaIdProduct":[{"id":"eca7948c-ddb7-37d1-9642-03286810298b","product":{"name":"angular-expressions","vendor":{"name":"peerigon"}},"product_version":"\u003c 1.1.2"}],"enisaIdVendor":[{"id":"b271714b-5bd1-3198-b03b-e48d38faf468","vendor":{"name":"peerigon"}}],"enisaIdVulnerability":[{"id":"3a016272-d186-3750-a881-0b40432dfa71","vulnerability":{"id":"GHSA-j6px-jwvv-vpwq","description":"Angular Expressions - Remote Code Execution","datePublished":"Feb 1, 2021, 3:01:26 PM","dateUpdated":"Oct 20, 2022, 1:26:13 PM","baseScore":null,"references":"https://github.com/peerigon/angular-expressions/security/advisories/GHSA-j6px-jwvv-vpwq\nhttps://nvd.nist.gov/vuln/detail/CVE-2021-21277\nhttps://github.com/peerigon/angular-expressions/commit/07edb62902b1f6127b3dcc013da61c6316dd0bf1\nhttps://www.npmjs.com/package/angular-expressions\nhttp://blog.angularjs.org/2016/09/angular-16-expression-sandbox-removal.html\n","enisa_id":"EUVD-2021-0555\n","aliases":"CVE-2021-21277\nGHSA-j6px-jwvv-vpwq\n","epss":0.0,"dataProcessed":"Nov 15, 2026, 2:05:47 AM","vulnerabilityProduct":[],"vulnerabilityVendor":[]}},{"id":"b33a158e-64b9-328b-97d7-86e389b90abf","vulnerability":{"id":"CVE-2021-21277","description":"angular-expressions is \"angular\u0027s nicest part extracted as a standalone module for the browser and node\". In angular-expressions before version 1.1.2 there is a vulnerability which allows Remote Code Execution if you call \"expressions.compile(userControlledInput)\" where \"userControlledInput\" is text that comes from user input. The security of the package could be bypassed by using a more complex payload, using a \".constructor.constructor\" technique. In terms of impact: 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. This is fixed in version 1.1.2 of angular-expressions A temporary workaround might be either to disable user-controlled input that will be fed into angular-expressions in your application or allow only following characters in the userControlledInput.","datePublished":"Feb 1, 2021, 3:05:24 PM","dateUpdated":"Aug 3, 2024, 6:09:15 PM","status":"PUBLISHED","baseScore":8.5,"baseScoreVersion":"3.1","baseScoreVector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:N","references":"https://github.com/peerigon/angular-expressions/security/advisories/GHSA-j6px-jwvv-vpwq\nhttps://www.npmjs.com/package/angular-expressions\nhttp://blog.angularjs.org/2016/09/angular-16-expression-sandbox-removal.html\nhttps://github.com/peerigon/angular-expressions/commit/07edb62902b1f6127b3dcc013da61c6316dd0bf1\n","enisa_id":"EUVD-2021-0555\n","assigner":"GitHub_M","epss":2.85,"dataProcessed":"Nov 17, 2026, 7:24:32 AM","vulnerabilityProduct":[{"id":"2b2f7af8-8f6a-3f11-94c2-31f186fd5baf","product":{"name":"angular-expressions","vendor":{"name":"peerigon"}},"product_version":"\u003c 1.1.2"}],"vulnerabilityVendor":[{"id":"5abf1c9e-a178-322e-9019-ee449a853e84","vendor":{"name":"peerigon"}}]}}],"enisaIdAdvisory":[]}