<?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>Sat, 03 Oct 2026 09:52:29 +0000</lastBuildDate>
    <item>
      <title>bdu:2023-04915</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2023-04915</link>
      <description>bdu:2023-04915</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2023-04915</guid>
    </item>
    <item>
      <title>Withdrawn: BELL-CVE-2023-30585 — CVE-2023-30585 does not affect BellSoft software</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2023-30585</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-30585</guid>
    </item>
    <item>
      <title>BIT-node-2023-30585</title>
      <link>https://cve.radiocsirt.org/vuln/bit-node-2023-30585</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: node&lt;/p&gt;
&lt;p&gt;A vulnerability has been identified in the Node.js (.msi version) installation process, specifically affecting Windows users who install Node.js using the .msi installer. This vulnerability emerges during the repair operation, where the &amp;#34;msiexec.exe&amp;#34; process, running under the NT AUTHORITY\SYSTEM context, attempts to read the %USERPROFILE% environment variable from the current user&amp;#39;s registry.&lt;/p&gt;
&lt;p&gt;The issue arises when the path referenced by the %USERPROFILE% environment variable does not exist. In such cases, the &amp;#34;msiexec.exe&amp;#34; process attempts to create the specified path in an unsafe manner, potentially leading to the creation of arbitrary folders in arbitrary locations.&lt;/p&gt;
&lt;p&gt;The severity of this vulnerability is heightened by the fact that the %USERPROFILE% environment variable in the Windows registry can be modified by standard (or &amp;#34;non-privileged&amp;#34;) users. Consequently, unprivileged actors, including malicious entities or trojans, can manipulate the environment variable key to deceive the privileged &amp;#34;msiexec.exe&amp;#34; process. This manipulation can result in the creation of folders in unintended and potentially malicious locations.&lt;/p&gt;
&lt;p&gt;It is important to note that this vulnerability is specific to Windows users who install Node.js using the .msi installer. Users who opt for other installation methods are not affected by this particular issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: node&lt;/p&gt;
&lt;p&gt;A vulnerability has been identified in the Node.js (.msi version) installation process, specifically affecting Windows users who install Node.js using the .msi installer. This vulnerability emerges during the repair operation, where the &amp;#34;msiexec.exe&amp;#34; process, running under the NT AUTHORITY\SYSTEM context, attempts to read the %USERPROFILE% environment variable from the current user&amp;#39;s registry.&lt;/p&gt;
&lt;p&gt;The issue arises when the path referenced by the %USERPROFILE% environment variable does not exist. In such cases, the &amp;#34;msiexec.exe&amp;#34; process attempts to create the specified path in an unsafe manner, potentially leading to the creation of arbitrary folders in arbitrary locations.&lt;/p&gt;
&lt;p&gt;The severity of this vulnerability is heightened by the fact that the %USERPROFILE% environment variable in the Windows registry can be modified by standard (or &amp;#34;non-privileged&amp;#34;) users. Consequently, unprivileged actors, including malicious entities or trojans, can manipulate the environment variable key to deceive the privileged &amp;#34;msiexec.exe&amp;#34; process. This manipulation can result in the creation of folders in unintended and potentially malicious locations.&lt;/p&gt;
&lt;p&gt;It is important to note that this vulnerability is specific to Windows users who install Node.js using the .msi installer. Users who opt for other installation methods are not affected by this particular issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bit-node-2023-30585</guid>
    </item>
    <item>
      <title>certfr-2023-avi-0862 — De multiples vulnérabilités ont été découvertes dans Oracle Java SE.
Elles permettent à un attaquant de provoquer un dé…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2023-avi-0862</link>
      <description>certfr-2023-avi-0862</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2023-avi-0862</guid>
    </item>
    <item>
      <title>EUVD-2026-258409</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-258409</link>
      <description>EUVD-2026-258409</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-258409</guid>
    </item>
    <item>
      <title>fkie_cve-2023-30585</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-30585</link>
      <description>&lt;p&gt;A vulnerability has been identified in the Node.js (.msi version) installation process, specifically affecting Windows users who install Node.js using the .msi installer. This vulnerability emerges during the repair operation, where the &amp;#34;msiexec.exe&amp;#34; process, running under the NT AUTHORITY\SYSTEM context, attempts to read the %USERPROFILE% environment variable from the current user&amp;#39;s registry.&lt;/p&gt;
&lt;p&gt;The issue arises when the path referenced by the %USERPROFILE% environment variable does not exist. In such cases, the &amp;#34;msiexec.exe&amp;#34; process attempts to create the specified path in an unsafe manner, potentially leading to the creation of arbitrary folders in arbitrary locations.&lt;/p&gt;
&lt;p&gt;The severity of this vulnerability is heightened by the fact that the %USERPROFILE% environment variable in the Windows registry can be modified by standard (or &amp;#34;non-privileged&amp;#34;) users. Consequently, unprivileged actors, including malicious entities or trojans, can manipulate the environment variable key to deceive the privileged &amp;#34;msiexec.exe&amp;#34; process. This manipulation can result in the creation of folders in unintended and potentially malicious locations.&lt;/p&gt;
&lt;p&gt;It is important to note that this vulnerability is specific to Windows users who install Node.js using the .msi installer. Users who opt for other installation methods are not affected by this particular issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;A vulnerability has been identified in the Node.js (.msi version) installation process, specifically affecting Windows users who install Node.js using the .msi installer. This vulnerability emerges during the repair operation, where the &amp;#34;msiexec.exe&amp;#34; process, running under the NT AUTHORITY\SYSTEM context, attempts to read the %USERPROFILE% environment variable from the current user&amp;#39;s registry.&lt;/p&gt;
&lt;p&gt;The issue arises when the path referenced by the %USERPROFILE% environment variable does not exist. In such cases, the &amp;#34;msiexec.exe&amp;#34; process attempts to create the specified path in an unsafe manner, potentially leading to the creation of arbitrary folders in arbitrary locations.&lt;/p&gt;
&lt;p&gt;The severity of this vulnerability is heightened by the fact that the %USERPROFILE% environment variable in the Windows registry can be modified by standard (or &amp;#34;non-privileged&amp;#34;) users. Consequently, unprivileged actors, including malicious entities or trojans, can manipulate the environment variable key to deceive the privileged &amp;#34;msiexec.exe&amp;#34; process. This manipulation can result in the creation of folders in unintended and potentially malicious locations.&lt;/p&gt;
&lt;p&gt;It is important to note that this vulnerability is specific to Windows users who install Node.js using the .msi installer. Users who opt for other installation methods are not affected by this particular issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-30585</guid>
    </item>
    <item>
      <title>GHSA-4r2r-cf85-vmc7</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-4r2r-cf85-vmc7</link>
      <description>&lt;p&gt;A vulnerability has been identified in the Node.js (.msi version) installation process, specifically affecting Windows users who install Node.js using the .msi installer. This vulnerability emerges during the repair operation, where the &amp;#34;msiexec.exe&amp;#34; process, running under the NT AUTHORITY\SYSTEM context, attempts to read the %USERPROFILE% environment variable from the current user&amp;#39;s registry.&lt;/p&gt;
&lt;p&gt;The issue arises when the path referenced by the %USERPROFILE% environment variable does not exist. In such cases, the &amp;#34;msiexec.exe&amp;#34; process attempts to create the specified path in an unsafe manner, potentially leading to the creation of arbitrary folders in arbitrary locations.&lt;/p&gt;
&lt;p&gt;The severity of this vulnerability is heightened by the fact that the %USERPROFILE% environment variable in the Windows registry can be modified by standard (or &amp;#34;non-privileged&amp;#34;) users. Consequently, unprivileged actors, including malicious entities or trojans, can manipulate the environment variable key to deceive the privileged &amp;#34;msiexec.exe&amp;#34; process. This manipulation can result in the creation of folders in unintended and potentially malicious locations.&lt;/p&gt;
&lt;p&gt;It is important to note that this vulnerability is specific to Windows users who install Node.js using the .msi installer. Users who opt for other installation methods are not affected by this particular issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;A vulnerability has been identified in the Node.js (.msi version) installation process, specifically affecting Windows users who install Node.js using the .msi installer. This vulnerability emerges during the repair operation, where the &amp;#34;msiexec.exe&amp;#34; process, running under the NT AUTHORITY\SYSTEM context, attempts to read the %USERPROFILE% environment variable from the current user&amp;#39;s registry.&lt;/p&gt;
&lt;p&gt;The issue arises when the path referenced by the %USERPROFILE% environment variable does not exist. In such cases, the &amp;#34;msiexec.exe&amp;#34; process attempts to create the specified path in an unsafe manner, potentially leading to the creation of arbitrary folders in arbitrary locations.&lt;/p&gt;
&lt;p&gt;The severity of this vulnerability is heightened by the fact that the %USERPROFILE% environment variable in the Windows registry can be modified by standard (or &amp;#34;non-privileged&amp;#34;) users. Consequently, unprivileged actors, including malicious entities or trojans, can manipulate the environment variable key to deceive the privileged &amp;#34;msiexec.exe&amp;#34; process. This manipulation can result in the creation of folders in unintended and potentially malicious locations.&lt;/p&gt;
&lt;p&gt;It is important to note that this vulnerability is specific to Windows users who install Node.js using the .msi installer. Users who opt for other installation methods are not affected by this particular issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-4r2r-cf85-vmc7</guid>
    </item>
    <item>
      <title>gsd-2023-30585</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2023-30585</link>
      <description>gsd-2023-30585</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2023-30585</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>SUSE-SU-2023:2655-1 — Security update for nodejs16</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2023:2655-1</link>
      <description>&lt;p&gt;Security update for nodejs16&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for nodejs16&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2023:2655-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>
