<?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>Wed, 07 Oct 2026 18:25:43 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-39518 — Junos OS: MX240, MX480, MX960 platforms using MPC10E: Memory leak will be observed when subscribed to a specific subscr…</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2024-39518</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Juniper Networks Junos OS, juniper junos_os&lt;/p&gt;
&lt;p&gt;A Heap-based Buffer Overflow vulnerability in the telemetry sensor process (sensord) of Juniper Networks Junos OS on MX240, MX480, MX960 platforms using MPC10E causes a steady increase in memory utilization, ultimately leading to a Denial of Service (DoS).&lt;/p&gt;
&lt;p&gt;When the device is subscribed to a specific subscription on Junos Telemetry Interface, a slow memory leak occurs and eventually all resources are consumed and the device becomes unresponsive. A manual reboot of the Line Card will be required to restore the device to its normal functioning.&lt;/p&gt;
&lt;p&gt;This issue is only seen when telemetry subscription is active.&lt;/p&gt;
&lt;p&gt;The Heap memory utilization can be monitored using the following command:
  &amp;gt; show system processes extensive&lt;/p&gt;
&lt;p&gt;The following command can be used to monitor the memory utilization of the specific sensor
  &amp;gt; show system info | match sensord
   PID   NAME                 MEMORY     PEAK MEMORY    %CPU   THREAD-COUNT CORE-AFFINITY   UPTIME&lt;/p&gt;
&lt;p&gt;1986  sensord            877.57MB   877.57MB         2       4           0,2-15          7-21:41:32&lt;/p&gt;
&lt;p&gt;This issue affects Junos OS:&lt;/p&gt;
&lt;p&gt;*  from 21.2R3-S5 before 21.2R3-S7, 
  *  from 21.4R3-S4 before 21.4R3-S6, 
  *  from 22.2R3 before 22.2R3-S4, 
  *  from 22.3R2 before 22.3R3-S2, 
  *  from 22.4R1 before 22.4R3, 
  *  from 23.2R1 before 23.2R2.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Juniper Networks Junos OS, juniper junos_os&lt;/p&gt;
&lt;p&gt;A Heap-based Buffer Overflow vulnerability in the telemetry sensor process (sensord) of Juniper Networks Junos OS on MX240, MX480, MX960 platforms using MPC10E causes a steady increase in memory utilization, ultimately leading to a Denial of Service (DoS).&lt;/p&gt;
&lt;p&gt;When the device is subscribed to a specific subscription on Junos Telemetry Interface, a slow memory leak occurs and eventually all resources are consumed and the device becomes unresponsive. A manual reboot of the Line Card will be required to restore the device to its normal functioning.&lt;/p&gt;
&lt;p&gt;This issue is only seen when telemetry subscription is active.&lt;/p&gt;
&lt;p&gt;The Heap memory utilization can be monitored using the following command:
  &amp;gt; show system processes extensive&lt;/p&gt;
&lt;p&gt;The following command can be used to monitor the memory utilization of the specific sensor
  &amp;gt; show system info | match sensord
   PID   NAME                 MEMORY     PEAK MEMORY    %CPU   THREAD-COUNT CORE-AFFINITY   UPTIME&lt;/p&gt;
&lt;p&gt;1986  sensord            877.57MB   877.57MB         2       4           0,2-15          7-21:41:32&lt;/p&gt;
&lt;p&gt;This issue affects Junos OS:&lt;/p&gt;
&lt;p&gt;*  from 21.2R3-S5 before 21.2R3-S7, 
  *  from 21.4R3-S4 before 21.4R3-S6, 
  *  from 22.2R3 before 22.2R3-S4, 
  *  from 22.3R2 before 22.3R3-S2, 
  *  from 22.4R1 before 22.4R3, 
  *  from 23.2R1 before 23.2R2.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2024-39518</guid>
    </item>
  </channel>
</rss>
