<?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>Mon, 05 Oct 2026 02:18:19 +0000</lastBuildDate>
    <item>
      <title>bdu:2023-04337</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2023-04337</link>
      <description>bdu:2023-04337</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2023-04337</guid>
    </item>
    <item>
      <title>certfr-2023-avi-0526 — De multiples vulnérabilités ont été découvertes dans les produits
Siemens. Certaines d'entre elles permettent à un atta…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2023-avi-0526</link>
      <description>certfr-2023-avi-0526</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2023-avi-0526</guid>
    </item>
    <item>
      <title>cnvd-2023-56540</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2023-56540</link>
      <description>cnvd-2023-56540</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2023-56540</guid>
    </item>
    <item>
      <title>EUVD-2026-203197</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-203197</link>
      <description>EUVD-2026-203197</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-203197</guid>
    </item>
    <item>
      <title>fkie_cve-2023-36521</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-36521</link>
      <description>&lt;p&gt;A vulnerability has been identified in SIMATIC MV540 H (All versions &amp;lt; V3.3.4), SIMATIC MV540 S (All versions &amp;lt; V3.3.4), SIMATIC MV550 H (All versions &amp;lt; V3.3.4), SIMATIC MV550 S (All versions &amp;lt; V3.3.4), SIMATIC MV560 U (All versions &amp;lt; V3.3.4), SIMATIC MV560 X (All versions &amp;lt; V3.3.4). The result synchronization server of the affected products contains a&#13;
vulnerability that may lead to a denial of service condition. An attacker may&#13;
cause a denial of service situation of all socket-based communication of the&#13;
affected products if the result server is enabled.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;A vulnerability has been identified in SIMATIC MV540 H (All versions &amp;lt; V3.3.4), SIMATIC MV540 S (All versions &amp;lt; V3.3.4), SIMATIC MV550 H (All versions &amp;lt; V3.3.4), SIMATIC MV550 S (All versions &amp;lt; V3.3.4), SIMATIC MV560 U (All versions &amp;lt; V3.3.4), SIMATIC MV560 X (All versions &amp;lt; V3.3.4). The result synchronization server of the affected products contains a&#13;
vulnerability that may lead to a denial of service condition. An attacker may&#13;
cause a denial of service situation of all socket-based communication of the&#13;
affected products if the result server is enabled.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-36521</guid>
    </item>
    <item>
      <title>GHSA-g2ch-vrrq-vf7w</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-g2ch-vrrq-vf7w</link>
      <description>&lt;p&gt;A vulnerability has been identified in SIMATIC MV540 H (All versions &amp;lt; V3.3.4), SIMATIC MV540 S (All versions &amp;lt; V3.3.4), SIMATIC MV550 H (All versions &amp;lt; V3.3.4), SIMATIC MV550 S (All versions &amp;lt; V3.3.4), SIMATIC MV560 U (All versions &amp;lt; V3.3.4), SIMATIC MV560 X (All versions &amp;lt; V3.3.4). The result synchronization server of the affected products contains a
vulnerability that may lead to a denial of service condition. An attacker may
cause a denial of service situation of all socket-based communication of the
affected products if the result server is enabled.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;A vulnerability has been identified in SIMATIC MV540 H (All versions &amp;lt; V3.3.4), SIMATIC MV540 S (All versions &amp;lt; V3.3.4), SIMATIC MV550 H (All versions &amp;lt; V3.3.4), SIMATIC MV550 S (All versions &amp;lt; V3.3.4), SIMATIC MV560 U (All versions &amp;lt; V3.3.4), SIMATIC MV560 X (All versions &amp;lt; V3.3.4). The result synchronization server of the affected products contains a
vulnerability that may lead to a denial of service condition. An attacker may
cause a denial of service situation of all socket-based communication of the
affected products if the result server is enabled.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-g2ch-vrrq-vf7w</guid>
    </item>
    <item>
      <title>gsd-2023-36521</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2023-36521</link>
      <description>gsd-2023-36521</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2023-36521</guid>
    </item>
    <item>
      <title>ICSA-23-194-04 — Siemens SIMATIC MV500 Devices</title>
      <link>https://cve.radiocsirt.org/vuln/icsa-23-194-04</link>
      <description>&lt;p&gt;In libtirpc before 1.3.3rc1, remote attackers could exhaust the file descriptors of a process that uses libtirpc because idle TCP connections are mishandled. This can, in turn, lead to an svc_run infinite loop without accepting new connections. A memory leak problem was found in the TCP source port generation algorithm in net/ipv4/tcp.c due to the small table perturb size. This flaw may allow an attacker to information leak and may cause a denial of service problem. 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 server could use this flaw to send trial messages to the server and record the time taken to process them. After a sufficiently large number of messages the attacker could recover the pre-master secret used for the original connection and thus be able to decrypt the application data sent over that connection. The function PEM_read_bio_ex() reads a PEM file from a BIO and parses and decodes the &amp;#34;name&amp;#34; (e.g. &amp;#34;CERTIFICATE&amp;#34;), any header da…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In libtirpc before 1.3.3rc1, remote attackers could exhaust the file descriptors of a process that uses libtirpc because idle TCP connections are mishandled. This can, in turn, lead to an svc_run infinite loop without accepting new connections. A memory leak problem was found in the TCP source port generation algorithm in net/ipv4/tcp.c due to the small table perturb size. This flaw may allow an attacker to information leak and may cause a denial of service problem. 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 server could use this flaw to send trial messages to the server and record the time taken to process them. After a sufficiently large number of messages the attacker could recover the pre-master secret used for the original connection and thus be able to decrypt the application data sent over that connection. The function PEM_read_bio_ex() reads a PEM file from a BIO and parses and decodes the &amp;#34;name&amp;#34; (e.g. &amp;#34;CERTIFICATE&amp;#34;), any header da…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/icsa-23-194-04</guid>
    </item>
  </channel>
</rss>
