<?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>Fri, 02 Oct 2026 17:15:19 +0000</lastBuildDate>
    <item>
      <title>bdu:2023-04928</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2023-04928</link>
      <description>bdu:2023-04928</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2023-04928</guid>
    </item>
    <item>
      <title>Withdrawn: BELL-CVE-2023-30583 — CVE-2023-30583 does not affect BellSoft software</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2023-30583</link>
      <description>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2023-30583</guid>
    </item>
    <item>
      <title>BIT-node-2023-30583</title>
      <link>https://cve.radiocsirt.org/vuln/bit-node-2023-30583</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: node&lt;/p&gt;
&lt;p&gt;fs.openAsBlob() can bypass the experimental permission model when using the file system read restriction with the `--allow-fs-read` flag in Node.js 20. This flaw arises from a missing check in the `fs.openAsBlob()` API.&lt;/p&gt;
&lt;p&gt;Please note that at the time this CVE was issued, the permission model is an experimental feature of Node.js.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: node&lt;/p&gt;
&lt;p&gt;fs.openAsBlob() can bypass the experimental permission model when using the file system read restriction with the `--allow-fs-read` flag in Node.js 20. This flaw arises from a missing check in the `fs.openAsBlob()` API.&lt;/p&gt;
&lt;p&gt;Please note that at the time this CVE was issued, the permission model is an experimental feature of Node.js.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bit-node-2023-30583</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0119 — De multiples vulnérabilités ont été découvertes dans &lt;span
class="textit"&gt;les produits Siemens&lt;/span&gt;. Certaines d'entr…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2024-avi-0119</link>
      <description>certfr-2024-avi-0119</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-0119</guid>
    </item>
    <item>
      <title>EUVD-2026-236184</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-236184</link>
      <description>EUVD-2026-236184</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-236184</guid>
    </item>
    <item>
      <title>fkie_cve-2023-30583</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-30583</link>
      <description>&lt;p&gt;fs.openAsBlob() can bypass the experimental permission model when using the file system read restriction with the `--allow-fs-read` flag in Node.js 20. This flaw arises from a missing check in the `fs.openAsBlob()` API.&lt;/p&gt;
&lt;p&gt;Please note that at the time this CVE was issued, the permission model is an experimental feature of Node.js.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;fs.openAsBlob() can bypass the experimental permission model when using the file system read restriction with the `--allow-fs-read` flag in Node.js 20. This flaw arises from a missing check in the `fs.openAsBlob()` API.&lt;/p&gt;
&lt;p&gt;Please note that at the time this CVE was issued, the permission model is an experimental feature of Node.js.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-30583</guid>
    </item>
    <item>
      <title>GHSA-9ccp-4gjg-264g</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-9ccp-4gjg-264g</link>
      <description>&lt;p&gt;fs.openAsBlob() can bypass the experimental permission model when using the file system read restriction with the `--allow-fs-read` flag in Node.js 20. This flaw arises from a missing check in the `fs.openAsBlob()` API.&lt;/p&gt;
&lt;p&gt;Please note that at the time this CVE was issued, the permission model is an experimental feature of Node.js.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;fs.openAsBlob() can bypass the experimental permission model when using the file system read restriction with the `--allow-fs-read` flag in Node.js 20. This flaw arises from a missing check in the `fs.openAsBlob()` API.&lt;/p&gt;
&lt;p&gt;Please note that at the time this CVE was issued, the permission model is an experimental feature of Node.js.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-9ccp-4gjg-264g</guid>
    </item>
    <item>
      <title>gsd-2023-30583</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2023-30583</link>
      <description>gsd-2023-30583</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2023-30583</guid>
    </item>
    <item>
      <title>ICSA-24-046-15 — Siemens SINEC NMS</title>
      <link>https://cve.radiocsirt.org/vuln/icsa-24-046-15</link>
      <description>&lt;p&gt;A read buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint checking. Note that this occurs after certificate chain signature verification and requires either a CA to have signed the malicious certificate or for the application to continue certificate verification despite failure to construct a path to a trusted issuer. The read buffer overrun might result in a crash which could lead to a denial of service attack. In theory it could also result in the disclosure of private memory contents (such as private keys, or sensitive plaintext) although we are not aware of any working exploit leading to memory contents disclosure as of the time of release of this advisory. In a TLS client, this can be triggered by connecting to a malicious server. In a TLS server, this can be triggered if the server requests client authentication and a malicious client connects. A timing based side channel exists in the OpenSSL RSA Decryption implementation which could be sufficient to recover a plaintext across a network in a Bleichenbacher style attack. To achieve a successful decryption an attacker would have to be able to send a very large number of trial messages for decryption. The vulnerability affects all RSA padding modes: PKCS#1 v1.5, RSA-OEAP and RSASVE. For example, in a TLS connection, RSA is commonly used by a client to send an encrypted pre-master secret to the server. An attacker that had observed a genuine connection between a client and a…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;A read buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint checking. Note that this occurs after certificate chain signature verification and requires either a CA to have signed the malicious certificate or for the application to continue certificate verification despite failure to construct a path to a trusted issuer. The read buffer overrun might result in a crash which could lead to a denial of service attack. In theory it could also result in the disclosure of private memory contents (such as private keys, or sensitive plaintext) although we are not aware of any working exploit leading to memory contents disclosure as of the time of release of this advisory. In a TLS client, this can be triggered by connecting to a malicious server. In a TLS server, this can be triggered if the server requests client authentication and a malicious client connects. A timing based side channel exists in the OpenSSL RSA Decryption implementation which could be sufficient to recover a plaintext across a network in a Bleichenbacher style attack. To achieve a successful decryption an attacker would have to be able to send a very large number of trial messages for decryption. The vulnerability affects all RSA padding modes: PKCS#1 v1.5, RSA-OEAP and RSASVE. For example, in a TLS connection, RSA is commonly used by a client to send an encrypted pre-master secret to the server. An attacker that had observed a genuine connection between a client and a…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/icsa-24-046-15</guid>
    </item>
    <item>
      <title>openSUSE-SU-2024:13021-1 — corepack20-20.3.1-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2024:13021-1</link>
      <description>&lt;p&gt;corepack20-20.3.1-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;corepack20-20.3.1-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2024:13021-1</guid>
    </item>
    <item>
      <title>WID-SEC-W-2023-1523 — Node.js: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2023-1523</link>
      <description>&lt;p&gt;Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in Node.js ausnutzen, um seine Privilegien zu erweitern, Dateien zu manipulieren, einen Denial of Service Zustand herbeizuführen, Informationen offenzulegen oder Sicherheitsvorkehrungen zu umgehen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in Node.js ausnutzen, um seine Privilegien zu erweitern, Dateien zu manipulieren, einen Denial of Service Zustand herbeizuführen, Informationen offenzulegen oder Sicherheitsvorkehrungen zu umgehen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2023-1523</guid>
    </item>
  </channel>
</rss>
