<?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, 12 Oct 2026 18:21:51 +0000</lastBuildDate>
    <item>
      <title>cnvd-2020-01923</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2020-01923</link>
      <description>cnvd-2020-01923</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2020-01923</guid>
    </item>
    <item>
      <title>EUVD-2026-55752</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-55752</link>
      <description>EUVD-2026-55752</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-55752</guid>
    </item>
    <item>
      <title>fkie_cve-2019-13465</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2019-13465</link>
      <description>&lt;p&gt;An issue was discovered in the ROS communications-related packages (aka ros_comm or ros-melodic-ros-comm) through 1.14.3. ROS_ASSERT_MSG only works when ROS_ASSERT_ENABLED is defined. This leads to a problem in the remove() function in clients/roscpp/src/libros/spinner.cpp. When ROS_ASSERT_ENABLED is not defined, the iterator loop will run out of the scope of the array, and cause denial of service for other components (that depend on the communication-related functions of this package). NOTE: The reporter of this issue now believes it was a false alarm.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;An issue was discovered in the ROS communications-related packages (aka ros_comm or ros-melodic-ros-comm) through 1.14.3. ROS_ASSERT_MSG only works when ROS_ASSERT_ENABLED is defined. This leads to a problem in the remove() function in clients/roscpp/src/libros/spinner.cpp. When ROS_ASSERT_ENABLED is not defined, the iterator loop will run out of the scope of the array, and cause denial of service for other components (that depend on the communication-related functions of this package). NOTE: The reporter of this issue now believes it was a false alarm.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2019-13465</guid>
    </item>
    <item>
      <title>GHSA-4cwx-xrxh-9ff7</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-4cwx-xrxh-9ff7</link>
      <description>&lt;p&gt;An issue was discovered in the ROS communications-related packages (aka ros_comm or ros-melodic-ros-comm) through 1.14.3. ROS_ASSERT_MSG only works when ROS_ASSERT_ENABLED is defined. This leads to a problem in the remove() function in clients/roscpp/src/libros/spinner.cpp. When ROS_ASSERT_ENABLED is not defined, the iterator loop will run out of the scope of the array, and cause denial of service for other components (that depend on the communication-related functions of this package).&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;An issue was discovered in the ROS communications-related packages (aka ros_comm or ros-melodic-ros-comm) through 1.14.3. ROS_ASSERT_MSG only works when ROS_ASSERT_ENABLED is defined. This leads to a problem in the remove() function in clients/roscpp/src/libros/spinner.cpp. When ROS_ASSERT_ENABLED is not defined, the iterator loop will run out of the scope of the array, and cause denial of service for other components (that depend on the communication-related functions of this package).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-4cwx-xrxh-9ff7</guid>
    </item>
    <item>
      <title>gsd-2019-13465</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2019-13465</link>
      <description>gsd-2019-13465</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2019-13465</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2019-13465</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2019-13465</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: ros-ros-comm, Ubuntu:18.04:LTS: ros-ros-comm&lt;/p&gt;
&lt;p&gt;An issue was discovered in the ROS communications-related packages (aka ros_comm or ros-melodic-ros-comm) through 1.14.3. ROS_ASSERT_MSG only works when ROS_ASSERT_ENABLED is defined. This leads to a problem in the remove() function in clients/roscpp/src/libros/spinner.cpp. When ROS_ASSERT_ENABLED is not defined, the iterator loop will run out of the scope of the array, and cause denial of service for other components (that depend on the communication-related functions of this package). NOTE: The reporter of this issue now believes it was a false alarm.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: ros-ros-comm, Ubuntu:18.04:LTS: ros-ros-comm&lt;/p&gt;
&lt;p&gt;An issue was discovered in the ROS communications-related packages (aka ros_comm or ros-melodic-ros-comm) through 1.14.3. ROS_ASSERT_MSG only works when ROS_ASSERT_ENABLED is defined. This leads to a problem in the remove() function in clients/roscpp/src/libros/spinner.cpp. When ROS_ASSERT_ENABLED is not defined, the iterator loop will run out of the scope of the array, and cause denial of service for other components (that depend on the communication-related functions of this package). NOTE: The reporter of this issue now believes it was a false alarm.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2019-13465</guid>
    </item>
  </channel>
</rss>
