GitHub Advisoryadvisory · npm

GHSA-hxhm-96pp-2m43 Remote Code Execution in Angular Expressions

HIGH Published 2020-01-24 Modified 2021-01-08 Official page ↗
Aliases
CVE-2020-5219
Ecosystem
npm
Packages
angular-expressions
Severity
High
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N
Weaknesses
CWE-74
Reviewed
2020-01-24

Affected packages

• npm angular-expressions: < 1.0.1 → fixed in 1.0.1

Description

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 For more information If you have any questions or comments about this advisory: • Open an issue in angular-expressions • Email us Credits The issue was reported by Maxime Nadeau from GoSecure, Inc.

Related

Alias · CVE (1)

  • CVE-2020-5219 Angular Expressions before version 1.0.1 has a remote code execution vulnerability if you call expressions.compile(userControlledInput)… vulnerability

Weakness · CWE (1)

  • CWE-74 Improper Neutralization of Special Elements in Output Used by a Downstream Component weakness

References