An attacker can write a malicious expression that escapes the sandbox to execute arbitrary code on the system.
Example of vulnerable code:
const expressions = require("angular-expressions");
const result = expressions.compile("__proto__.constructor")({}, {});
// result should be undefined, however for versions <=1.4.2, it returns an object.
With a more complex (undisclosed) payload, one can get full access to Arbitrary code execution on the system.
The problem has been patched in version 1.4.3 of angular-expressions.
There is one workaround if it not possible for you to update :
const result = expressions.compile("__proto__.constructor")({}); : in this case you lose the feature of locals if you need it.Credits go to JorianWoltjer who has found the issue and reported it to use. https://jorianwoltjer.com/
{
"cwe_ids": [
"CWE-94"
],
"github_reviewed": true,
"github_reviewed_at": "2024-12-10T16:54:50Z",
"nvd_published_at": "2024-12-10T16:15:23Z",
"severity": "CRITICAL"
}