<?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>Mon, 12 Oct 2026 15:42:30 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-30857 — @aedart/support possibly vulnerable to prototype pollution in metadata record, when using meta decorator</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2023-30857</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; aedart ion&lt;/p&gt;
&lt;p&gt;@aedart/support is the support package for Ion, a monorepo for JavaScript/TypeScript packages. Prior to version `0.6.1`, there is a possible prototype pollution issue for the `MetadataRecord`, when merged with a base class&amp;#39; metadata object, in `meta` decorator from the `@aedart/support` package. The likelihood of exploitation is questionable, given that a class&amp;#39;s metadata can only be set or altered when the class is decorated via `meta()`. Furthermore, object(s) of sensitive nature would have to be stored as metadata, before this can lead to a security impact. The issue has been patched in version `0.6.1`.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; aedart ion&lt;/p&gt;
&lt;p&gt;@aedart/support is the support package for Ion, a monorepo for JavaScript/TypeScript packages. Prior to version `0.6.1`, there is a possible prototype pollution issue for the `MetadataRecord`, when merged with a base class&amp;#39; metadata object, in `meta` decorator from the `@aedart/support` package. The likelihood of exploitation is questionable, given that a class&amp;#39;s metadata can only be set or altered when the class is decorated via `meta()`. Furthermore, object(s) of sensitive nature would have to be stored as metadata, before this can lead to a security impact. The issue has been patched in version `0.6.1`.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2023-30857</guid>
    </item>
  </channel>
</rss>
