https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 12:20:45 +0000 https://cve.radiocsirt.org/vuln/bdu:2024-09774 bdu:2024-09774 https://cve.radiocsirt.org/vuln/bdu:2024-09774 https://cve.radiocsirt.org/vuln/bell-cve-2023-32005 <p><strong>Withdrawn by the publisher.</strong></p> <p><strong>Withdrawn by the publisher.</strong></p> https://cve.radiocsirt.org/vuln/bell-cve-2023-32005 https://cve.radiocsirt.org/vuln/bit-node-2023-32005 <p><strong>Affected:</strong> Bitnami: node</p> <p>A vulnerability has been identified in Node.js version 20, affecting users of the experimental permission model when the --allow-fs-read flag is used with a non-* argument.</p> <p>This flaw arises from an inadequate permission model that fails to restrict file stats through the `fs.statfs` API. As a result, malicious actors can retrieve stats from files that they do not have explicit read access to.</p> <p>This vulnerability affects all users using the experimental permission model in Node.js 20.</p> <p>Please note that at the time this CVE was issued, the permission model is an experimental feature of Node.js.</p> <p><strong>Affected:</strong> Bitnami: node</p> <p>A vulnerability has been identified in Node.js version 20, affecting users of the experimental permission model when the --allow-fs-read flag is used with a non-* argument.</p> <p>This flaw arises from an inadequate permission model that fails to restrict file stats through the `fs.statfs` API. As a result, malicious actors can retrieve stats from files that they do not have explicit read access to.</p> <p>This vulnerability affects all users using the experimental permission model in Node.js 20.</p> <p>Please note that at the time this CVE was issued, the permission model is an experimental feature of Node.js.</p> https://cve.radiocsirt.org/vuln/bit-node-2023-32005 https://cve.radiocsirt.org/vuln/certfr-2024-avi-0119 certfr-2024-avi-0119 https://cve.radiocsirt.org/vuln/certfr-2024-avi-0119 https://cve.radiocsirt.org/vuln/euvd-2026-237118 EUVD-2026-237118 https://cve.radiocsirt.org/vuln/euvd-2026-237118 https://cve.radiocsirt.org/vuln/fkie_cve-2023-32005 <p>A vulnerability has been identified in Node.js version 20, affecting users of the experimental permission model when the --allow-fs-read flag is used with a non-* argument.</p> <p>This flaw arises from an inadequate permission model that fails to restrict file stats through the `fs.statfs` API. As a result, malicious actors can retrieve stats from files that they do not have explicit read access to.</p> <p>This vulnerability affects all users using the experimental permission model in Node.js 20.</p> <p>Please note that at the time this CVE was issued, the permission model is an experimental feature of Node.js.</p> <p>A vulnerability has been identified in Node.js version 20, affecting users of the experimental permission model when the --allow-fs-read flag is used with a non-* argument.</p> <p>This flaw arises from an inadequate permission model that fails to restrict file stats through the `fs.statfs` API. As a result, malicious actors can retrieve stats from files that they do not have explicit read access to.</p> <p>This vulnerability affects all users using the experimental permission model in Node.js 20.</p> <p>Please note that at the time this CVE was issued, the permission model is an experimental feature of Node.js.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2023-32005 https://cve.radiocsirt.org/vuln/ghsa-6hjf-ffg5-v8w7 <p>A vulnerability has been identified in Node.js version 20, affecting users of the experimental permission model when the --allow-fs-read flag is used with a non-* argument.</p> <p>This flaw arises from an inadequate permission model that fails to restrict file stats through the `fs.statfs` API. As a result, malicious actors can retrieve stats from files that they do not have explicit read access to.</p> <p>This vulnerability affects all users using the experimental permission model in Node.js 20.</p> <p>Please note that at the time this CVE was issued, the permission model is an experimental feature of Node.js.</p> <p>A vulnerability has been identified in Node.js version 20, affecting users of the experimental permission model when the --allow-fs-read flag is used with a non-* argument.</p> <p>This flaw arises from an inadequate permission model that fails to restrict file stats through the `fs.statfs` API. As a result, malicious actors can retrieve stats from files that they do not have explicit read access to.</p> <p>This vulnerability affects all users using the experimental permission model in Node.js 20.</p> <p>Please note that at the time this CVE was issued, the permission model is an experimental feature of Node.js.</p> https://cve.radiocsirt.org/vuln/ghsa-6hjf-ffg5-v8w7 https://cve.radiocsirt.org/vuln/gsd-2023-32005 gsd-2023-32005 https://cve.radiocsirt.org/vuln/gsd-2023-32005 https://cve.radiocsirt.org/vuln/icsa-24-046-15 <p>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…</p> <p>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…</p> https://cve.radiocsirt.org/vuln/icsa-24-046-15 https://cve.radiocsirt.org/vuln/opensuse-su-2024:13117-1 <p>corepack20-20.5.1-1.1 on GA media</p> <p>corepack20-20.5.1-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2024:13117-1 https://cve.radiocsirt.org/vuln/wid-sec-w-2023-2024 <p>Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in Node.js ausnutzen, um Sicherheitsvorkehrungen zu umgehen.</p> <p>Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in Node.js ausnutzen, um Sicherheitsvorkehrungen zu umgehen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2023-2024