https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 06 Oct 2026 14:17:00 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-22088 EUVD-2026-22088 https://cve.radiocsirt.org/vuln/euvd-2026-22088 https://cve.radiocsirt.org/vuln/fkie_cve-2021-21277 <p>angular-expressions is &#34;angular&#39;s nicest part extracted as a standalone module for the browser and node&#34;. In angular-expressions before version 1.1.2 there is a vulnerability which allows Remote Code Execution if you call &#34;expressions.compile(userControlledInput)&#34; where &#34;userControlledInput&#34; is text that comes from user input. The security of the package could be bypassed by using a more complex payload, using a &#34;.constructor.constructor&#34; 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.</p> <p>angular-expressions is &#34;angular&#39;s nicest part extracted as a standalone module for the browser and node&#34;. In angular-expressions before version 1.1.2 there is a vulnerability which allows Remote Code Execution if you call &#34;expressions.compile(userControlledInput)&#34; where &#34;userControlledInput&#34; is text that comes from user input. The security of the package could be bypassed by using a more complex payload, using a &#34;.constructor.constructor&#34; 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.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2021-21277 https://cve.radiocsirt.org/vuln/ghsa-j6px-jwvv-vpwq <p><strong>Affected:</strong> npm: angular-expressions</p> <p>### Impact</p> <p>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.</p> <p>This time, the security of the package could be bypassed by using a more complex payload, using a `.constructor.constructor` technique.</p> <p>* 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.</p> <p>### Patches</p> <p>Users should upgrade to version 1.1.2 of angular-expressions</p> <p>### Workarounds</p> <p>A temporary workaround might be either to :</p> <p>* disable user-controlled input that will be fed into angular-expressions in your application</p> <p>OR</p> <p>* allow only following characters in the userControlledInput :</p> <p>```js if (/^[|a-zA-Z.0-9 :&#34;&#39;+-?]+$/.test(userControlledInput)) { var result = expressions.compile(userControlledInput); } else { result = undefined; } ```</p> <p>### References</p> <p>[Removal of angular-expression sandbox](http://blog.angularjs.org/2016/09/angular-16-expression-sandbox-removal.html)</p> <p>### For more information</p> <p>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)</p> <p>### Credits</p> <p>The iss…</p> <p><strong>Affected:</strong> npm: angular-expressions</p> <p>### Impact</p> <p>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.</p> <p>This time, the security of the package could be bypassed by using a more complex payload, using a `.constructor.constructor` technique.</p> <p>* 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.</p> <p>### Patches</p> <p>Users should upgrade to version 1.1.2 of angular-expressions</p> <p>### Workarounds</p> <p>A temporary workaround might be either to :</p> <p>* disable user-controlled input that will be fed into angular-expressions in your application</p> <p>OR</p> <p>* allow only following characters in the userControlledInput :</p> <p>```js if (/^[|a-zA-Z.0-9 :&#34;&#39;+-?]+$/.test(userControlledInput)) { var result = expressions.compile(userControlledInput); } else { result = undefined; } ```</p> <p>### References</p> <p>[Removal of angular-expression sandbox](http://blog.angularjs.org/2016/09/angular-16-expression-sandbox-removal.html)</p> <p>### For more information</p> <p>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)</p> <p>### Credits</p> <p>The iss…</p> https://cve.radiocsirt.org/vuln/ghsa-j6px-jwvv-vpwq https://cve.radiocsirt.org/vuln/gsd-2021-21277 gsd-2021-21277 https://cve.radiocsirt.org/vuln/gsd-2021-21277