<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 06 Oct 2026 17:15:47 +0000</lastBuildDate>
    <item>
      <title>bdu:2024-11152</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2024-11152</link>
      <description>bdu:2024-11152</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2024-11152</guid>
    </item>
    <item>
      <title>EUVD-2026-206608</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-206608</link>
      <description>EUVD-2026-206608</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-206608</guid>
    </item>
    <item>
      <title>fkie_cve-2024-54152</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-54152</link>
      <description>&lt;p&gt;Angular Expressions provides expressions for the Angular.JS web framework as a standalone module. Prior to version 1.4.3, an attacker can write a malicious expression that escapes the sandbox to execute arbitrary code on the system. 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. Two possible workarounds are available. One may either disable access to `__proto__` globally or make sure that one uses the function with just one argument.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Angular Expressions provides expressions for the Angular.JS web framework as a standalone module. Prior to version 1.4.3, an attacker can write a malicious expression that escapes the sandbox to execute arbitrary code on the system. 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. Two possible workarounds are available. One may either disable access to `__proto__` globally or make sure that one uses the function with just one argument.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-54152</guid>
    </item>
    <item>
      <title>GHSA-5462-4vcx-jh7j — Angular Expressions - Remote Code Execution when using locals</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-5462-4vcx-jh7j</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: angular-expressions&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;An attacker can write a malicious expression that escapes the sandbox to execute arbitrary code on the system.&lt;/p&gt;
&lt;p&gt;Example of vulnerable code:&lt;/p&gt;
&lt;p&gt;```js
const expressions = require(&amp;#34;angular-expressions&amp;#34;);
const result = expressions.compile(&amp;#34;__proto__.constructor&amp;#34;)({}, {});
// result should be undefined, however for versions &amp;lt;=1.4.2, it returns an object.
```&lt;/p&gt;
&lt;p&gt;With a more complex (undisclosed) payload, one can get full access to Arbitrary code execution on the system.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;The problem has been patched in version 1.4.3 of angular-expressions.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;There is one workaround if it not possible for you to update :&lt;/p&gt;
&lt;p&gt;* Make sure that you use the compiled function with just one argument : ie this is not vulnerable : 
    `const result = expressions.compile(&amp;#34;__proto__.constructor&amp;#34;)({});` : in this case you lose the feature of locals if you need it.&lt;/p&gt;
&lt;p&gt;### Credits&lt;/p&gt;
&lt;p&gt;Credits go to [JorianWoltjer](https://github.com/JorianWoltjer) who has found the issue and reported it to use. https://jorianwoltjer.com/&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: angular-expressions&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;An attacker can write a malicious expression that escapes the sandbox to execute arbitrary code on the system.&lt;/p&gt;
&lt;p&gt;Example of vulnerable code:&lt;/p&gt;
&lt;p&gt;```js
const expressions = require(&amp;#34;angular-expressions&amp;#34;);
const result = expressions.compile(&amp;#34;__proto__.constructor&amp;#34;)({}, {});
// result should be undefined, however for versions &amp;lt;=1.4.2, it returns an object.
```&lt;/p&gt;
&lt;p&gt;With a more complex (undisclosed) payload, one can get full access to Arbitrary code execution on the system.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;The problem has been patched in version 1.4.3 of angular-expressions.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;There is one workaround if it not possible for you to update :&lt;/p&gt;
&lt;p&gt;* Make sure that you use the compiled function with just one argument : ie this is not vulnerable : 
    `const result = expressions.compile(&amp;#34;__proto__.constructor&amp;#34;)({});` : in this case you lose the feature of locals if you need it.&lt;/p&gt;
&lt;p&gt;### Credits&lt;/p&gt;
&lt;p&gt;Credits go to [JorianWoltjer](https://github.com/JorianWoltjer) who has found the issue and reported it to use. https://jorianwoltjer.com/&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-5462-4vcx-jh7j</guid>
    </item>
    <item>
      <title>Withdrawn: UBUNTU-CVE-2024-54152</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-54152</link>
      <description>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: angular.js, Ubuntu:18.04:LTS: angular.js, Ubuntu:20.04:LTS: angular.js, Ubuntu:22.04:LTS: angular.js, Ubuntu:24.04:LTS: angular.js, Ubuntu:25.10: angular.js, Ubuntu:25.04: angular.js&lt;/p&gt;
&lt;p&gt;Angular Expressions provides expressions for the Angular.JS web framework as a standalone module. Prior to version 1.4.3, an attacker can write a malicious expression that escapes the sandbox to execute arbitrary code on the system. 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. Two possible workarounds are available. One may either disable access to `__proto__` globally or make sure that one uses the function with just one argument.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: angular.js, Ubuntu:18.04:LTS: angular.js, Ubuntu:20.04:LTS: angular.js, Ubuntu:22.04:LTS: angular.js, Ubuntu:24.04:LTS: angular.js, Ubuntu:25.10: angular.js, Ubuntu:25.04: angular.js&lt;/p&gt;
&lt;p&gt;Angular Expressions provides expressions for the Angular.JS web framework as a standalone module. Prior to version 1.4.3, an attacker can write a malicious expression that escapes the sandbox to execute arbitrary code on the system. 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. Two possible workarounds are available. One may either disable access to `__proto__` globally or make sure that one uses the function with just one argument.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-54152</guid>
    </item>
  </channel>
</rss>
