https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 11:17:50 +0000 https://cve.radiocsirt.org/vuln/bdu:2024-09312 bdu:2024-09312 https://cve.radiocsirt.org/vuln/bdu:2024-09312 https://cve.radiocsirt.org/vuln/cnvd-2024-38019 cnvd-2024-38019 https://cve.radiocsirt.org/vuln/cnvd-2024-38019 https://cve.radiocsirt.org/vuln/euvd-2026-162453 EUVD-2026-162453 https://cve.radiocsirt.org/vuln/euvd-2026-162453 https://cve.radiocsirt.org/vuln/fkie_cve-2024-32006 <p>A vulnerability has been identified in SINEMA Remote Connect Client (All versions &lt; V3.2 SP2). The affected application does not expire the user session on reboot without logout. This could allow an attacker to bypass Multi-Factor Authentication.</p> <p>A vulnerability has been identified in SINEMA Remote Connect Client (All versions &lt; V3.2 SP2). The affected application does not expire the user session on reboot without logout. This could allow an attacker to bypass Multi-Factor Authentication.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2024-32006 https://cve.radiocsirt.org/vuln/ghsa-5v93-w7mf-hc4q <p>A vulnerability has been identified in SINEMA Remote Connect Client (All versions &lt; V3.2 SP2). The affected application does not expire the user session on reboot without logout. This could allow an attacker to bypass Multi-Factor Authentication.</p> <p>A vulnerability has been identified in SINEMA Remote Connect Client (All versions &lt; V3.2 SP2). The affected application does not expire the user session on reboot without logout. This could allow an attacker to bypass Multi-Factor Authentication.</p> https://cve.radiocsirt.org/vuln/ghsa-5v93-w7mf-hc4q https://cve.radiocsirt.org/vuln/gsd-2024-32006 gsd-2024-32006 https://cve.radiocsirt.org/vuln/gsd-2024-32006 https://cve.radiocsirt.org/vuln/icsa-24-256-10 <p>Use after free in OpenVPN version 2.6.0 to 2.6.6 may lead to undefined behavoir, leaking memory buffers or remote execution when sending network buffers to a remote peer. When a protocol selection parameter option disables all protocols without adding any then the default set of protocols would remain in the allowed set due to an error in the logic for removing protocols. The below command would perform a request to curl.se with a plaintext protocol which has been explicitly disabled. curl --proto -all,-http http://curl.se The flaw is only present if the set of selected protocols disables the entire set of available protocols, in itself a command with no practical use and therefore unlikely to be encountered in real situations. The curl security team has thus assessed this to be low severity bug. libcurl skips the certificate verification for a QUIC connection under certain conditions, when built to use wolfSSL. If told to use an unknown/bad cipher or curve, the error path accidentally skips the verification and returns OK, thus ignoring any certificate problems. When an application tells libcurl it wants to allow HTTP/2 server push, and the amount of received headers for the push surpasses the maximum allowed limit (1000), libcurl aborts the server push. When aborting, libcurl inadvertently does not free all the previously allocated headers and instead leaks the memory. Further, this error condition fails silently and is therefore not easily detected by an applicatio…</p> <p>Use after free in OpenVPN version 2.6.0 to 2.6.6 may lead to undefined behavoir, leaking memory buffers or remote execution when sending network buffers to a remote peer. When a protocol selection parameter option disables all protocols without adding any then the default set of protocols would remain in the allowed set due to an error in the logic for removing protocols. The below command would perform a request to curl.se with a plaintext protocol which has been explicitly disabled. curl --proto -all,-http http://curl.se The flaw is only present if the set of selected protocols disables the entire set of available protocols, in itself a command with no practical use and therefore unlikely to be encountered in real situations. The curl security team has thus assessed this to be low severity bug. libcurl skips the certificate verification for a QUIC connection under certain conditions, when built to use wolfSSL. If told to use an unknown/bad cipher or curve, the error path accidentally skips the verification and returns OK, thus ignoring any certificate problems. When an application tells libcurl it wants to allow HTTP/2 server push, and the amount of received headers for the push surpasses the maximum allowed limit (1000), libcurl aborts the server push. When aborting, libcurl inadvertently does not free all the previously allocated headers and instead leaks the memory. Further, this error condition fails silently and is therefore not easily detected by an applicatio…</p> https://cve.radiocsirt.org/vuln/icsa-24-256-10