https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 19:50:21 +0000 https://cve.radiocsirt.org/vuln/bdu:2024-01643 bdu:2024-01643 https://cve.radiocsirt.org/vuln/bdu:2024-01643 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/cnvd-2024-09309 cnvd-2024-09309 https://cve.radiocsirt.org/vuln/cnvd-2024-09309 https://cve.radiocsirt.org/vuln/euvd-2026-238728 EUVD-2026-238728 https://cve.radiocsirt.org/vuln/euvd-2026-238728 https://cve.radiocsirt.org/vuln/fkie_cve-2024-23810 <p>A vulnerability has been identified in SINEC NMS (All versions &lt; V2.0 SP1). The affected application is vulnerable to SQL injection. This could allow an unauthenticated remote attacker to execute arbitrary SQL queries on the server database.</p> <p>A vulnerability has been identified in SINEC NMS (All versions &lt; V2.0 SP1). The affected application is vulnerable to SQL injection. This could allow an unauthenticated remote attacker to execute arbitrary SQL queries on the server database.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2024-23810 https://cve.radiocsirt.org/vuln/ghsa-qf5j-fwc8-wj57 <p>A vulnerability has been identified in SINEC NMS (All versions &lt; V2.0 SP1). The affected application is vulnerable to SQL injection. This could allow an unauthenticated remote attacker to execute arbitrary SQL queries on the server database.</p> <p>A vulnerability has been identified in SINEC NMS (All versions &lt; V2.0 SP1). The affected application is vulnerable to SQL injection. This could allow an unauthenticated remote attacker to execute arbitrary SQL queries on the server database.</p> https://cve.radiocsirt.org/vuln/ghsa-qf5j-fwc8-wj57 https://cve.radiocsirt.org/vuln/gsd-2024-23810 gsd-2024-23810 https://cve.radiocsirt.org/vuln/gsd-2024-23810 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