Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.
Open advisories
4 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.
Impact An attacker can write a malicious expression that escapes the sandbox to execute arbitrary code on the system. Example of vulnerable code: This should throw the error : Filter 'proto' is not defined, however, this shows : Uncaught SyntaxError: Unexpected identifier 'Object' With a more complex (undisclosed) payload, one can get full access to Arbitrary code execution on the system. Vulnerable versions : angular-expressions <= 1.5.1 Patches The problem has been patched in version 1.5.2 of angular-expressions. Credits Credits go to San Gil from www.securityoffice.io who has found the issue and reported it to us.
Recommended action: Upgrade to 1.5.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Impact An attacker can write a malicious expression that escapes the sandbox to execute arbitrary code on the system. Example of vulnerable code: With a more complex (undisclosed) payload, one can get full access to Arbitrary code execution on the system. Patches The problem has been patched in version 1.4.3 of angular-expressions. Workarounds There is one workaround if it not possible for you to update : Make sure that you use the compiled function with just one argument : ie this is not vulnerable : const result = expressions.compile("proto.constructor")({}); : in this case you lose the feature of locals if you need it. Credits Credits go to JorianWoltjer who has found the issue and reported it to use. https://jorianwoltjer.com/
Recommended action: Upgrade to 1.4.3 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
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. This time, the security of the package could be bypassed by using a more complex payload, using a .constructor.constructor technique. 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.1.2 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 : References Removal of angular-expression sandbox For more information If you have any…
Recommended action: Upgrade to 1.1.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
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 : 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…
Recommended action: Upgrade to 1.0.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.