<?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>Sun, 04 Oct 2026 08:36:13 +0000</lastBuildDate>
    <item>
      <title>cnvd-2024-38018</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2024-38018</link>
      <description>cnvd-2024-38018</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2024-38018</guid>
    </item>
    <item>
      <title>EUVD-2026-162289</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-162289</link>
      <description>EUVD-2026-162289</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-162289</guid>
    </item>
    <item>
      <title>fkie_cve-2024-42344</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-42344</link>
      <description>&lt;p&gt;A vulnerability has been identified in SINEMA Remote Connect Client (All versions &amp;lt; V3.2 SP2). The affected application inserts sensitive information into a log file which is readable by all legitimate users of the underlying system. This could allow an authenticated attacker to compromise the confidentiality of other users&amp;#39; configuration data.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;A vulnerability has been identified in SINEMA Remote Connect Client (All versions &amp;lt; V3.2 SP2). The affected application inserts sensitive information into a log file which is readable by all legitimate users of the underlying system. This could allow an authenticated attacker to compromise the confidentiality of other users&amp;#39; configuration data.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-42344</guid>
    </item>
    <item>
      <title>GHSA-p868-fp4q-w4hx</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-p868-fp4q-w4hx</link>
      <description>&lt;p&gt;A vulnerability has been identified in SINEMA Remote Connect Client (All versions &amp;lt; V3.2 SP2). The affected application inserts sensitive information into a log file which is readable by all legitimate users of the underlying system. This could allow an authenticated attacker to compromise the confidentiality of other users&amp;#39; configuration data.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;A vulnerability has been identified in SINEMA Remote Connect Client (All versions &amp;lt; V3.2 SP2). The affected application inserts sensitive information into a log file which is readable by all legitimate users of the underlying system. This could allow an authenticated attacker to compromise the confidentiality of other users&amp;#39; configuration data.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-p868-fp4q-w4hx</guid>
    </item>
    <item>
      <title>ICSA-24-256-10 — Siemens SINEMA</title>
      <link>https://cve.radiocsirt.org/vuln/icsa-24-256-10</link>
      <description>&lt;p&gt;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…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/icsa-24-256-10</guid>
    </item>
  </channel>
</rss>
