<?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>Wed, 07 Oct 2026 12:52:19 +0000</lastBuildDate>
    <item>
      <title>CVE-2021-21277 — Angular Expressions - Remote Code Execution</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2021-21277</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; peerigon angular-expressions&lt;/p&gt;
&lt;p&gt;angular-expressions is &amp;#34;angular&amp;#39;s nicest part extracted as a standalone module for the browser and node&amp;#34;. In angular-expressions before version 1.1.2 there is a vulnerability which allows Remote Code Execution if you call &amp;#34;expressions.compile(userControlledInput)&amp;#34; where &amp;#34;userControlledInput&amp;#34; is text that comes from user input. The security of the package could be bypassed by using a more complex payload, using a &amp;#34;.constructor.constructor&amp;#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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; peerigon angular-expressions&lt;/p&gt;
&lt;p&gt;angular-expressions is &amp;#34;angular&amp;#39;s nicest part extracted as a standalone module for the browser and node&amp;#34;. In angular-expressions before version 1.1.2 there is a vulnerability which allows Remote Code Execution if you call &amp;#34;expressions.compile(userControlledInput)&amp;#34; where &amp;#34;userControlledInput&amp;#34; is text that comes from user input. The security of the package could be bypassed by using a more complex payload, using a &amp;#34;.constructor.constructor&amp;#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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2021-21277</guid>
    </item>
  </channel>
</rss>
