CVE-2020-5219
mediumpriority · track · 36EPSS 0.024 · 84 %ileEUUSEPSS · scored 2026-10-28
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.
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · medium–high · 6.8–8.8
weaknesses
The CWE weakness classes this flaw belongs to.
affected products (3)
Products and version ranges known to be affected.
advisories (1)
Vendor and ecosystem advisories describing this.
- GHSA-hxhm-96pp-2m43Remote Code Execution in Angular Expressions2020-01-24ghsa · osvUS
### Impact The vulnerability, reported by GoSecure Inc, allows Remote Code Execution, 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. ### Patches Users should upgrade to version 1.0.1 of angular-expressions ### Workarounds 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 : ```js if (/^[|a-zA-Z.0-9 :"'+-?]+$/.test(userControlledInput)) { var result = expressions.compile(userControlledInput); } else { result = undefined; } ``` ### References [Removal of angular-expression sandbox](http://blog.angularjs.org/2016/09/angular-16-expression-sandbox-removal.html) ### For more information If you have any questions or comments about this advisory: * Open an issue in [angular-expressions](https://github.com/peerigon/angular-expressions/issues) * [Email us](mailto:contact@javascript-ninja.fr) ### Credits The issue was reported by Maxime Nadeau from GoSecure, Inc.
also known as (3)
Other names and identifiers for this entity.
sources
Which sources assert this record, and when.
references (10)
External citations — patches, advisories, analysis.
- http://blog.angularjs.org/2016/09/angular-16-expression-sandbox-removal.htmlcnnvd
- https://github.com/peerigon/angular-expressions/commit/061addfb9a9e932a970e5fcb913d020038e65667cnnvd
- https://github.com/peerigon/angular-expressions/security/advisories/GHSA-hxhm-96pp-2m43cnnvd
- https://nvd.nist.gov/vuln/detail/CVE-2020-5219cnnvd
- http://blog.angularjs.org/2016/09/angular-16-expression-sandbox-removal.htmlenisa_euvd
- https://github.com/peerigon/angular-expressions/commit/061addfb9a9e932a970e5fcb913d020038e65667enisa_euvd
- https://github.com/peerigon/angular-expressions/security/advisories/GHSA-hxhm-96pp-2m43enisa_euvd
- http://blog.angularjs.org/2016/09/angular-16-expression-sandbox-removal.htmlVendor Advisorynvd
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan