<?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 05:15:34 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-21600 — Junos OS: PTX Series: In an FTI scenario MPLS packets hitting reject next-hop will cause a host path wedge condition</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2024-21600</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Juniper Networks Junos OS&lt;/p&gt;
&lt;p&gt;An Improper Neutralization of Equivalent Special Elements vulnerability in the Packet Forwarding Engine (PFE) of Juniper Networks Junos OS on PTX Series allows a unauthenticated, adjacent attacker to cause a Denial of Service (DoS).&lt;/p&gt;
&lt;p&gt;When MPLS packets are meant to be sent to a flexible tunnel interface (FTI) and if the FTI tunnel is down, these will hit the reject NH, due to which the packets get sent to the CPU and cause a host path wedge condition. This will cause the FPC to hang and requires a manual restart to recover.&lt;/p&gt;
&lt;p&gt;Please note that this issue specifically affects PTX1000, PTX3000, PTX5000 with FPC3, PTX10002-60C, and PTX10008/16 with LC110x. Other PTX Series devices and Line Cards (LC) are not affected.&lt;/p&gt;
&lt;p&gt;The following log message can be seen when the issue occurs:&lt;/p&gt;
&lt;p&gt;Cmerror Op Set: Host Loopback: HOST LOOPBACK WEDGE DETECTED IN PATH ID &amp;lt;id&amp;gt; (URI: /fpc/&amp;lt;fpc&amp;gt;/pfe/&amp;lt;pfe&amp;gt;/cm/&amp;lt;cm&amp;gt;/Host_Loopback/&amp;lt;cm&amp;gt;/HOST_LOOPBACK_MAKE_CMERROR_ID[&amp;lt;id&amp;gt;])
This issue affects Juniper Networks Junos OS:&lt;/p&gt;
&lt;p&gt;*  All versions earlier than 20.4R3-S8;
  *  21.1 versions earlier than 21.1R3-S4;
  *  21.2 versions earlier than 21.2R3-S6;
  *  21.3 versions earlier than 21.3R3-S3;
  *  21.4 versions earlier than 21.4R3-S5;
  *  22.1 versions earlier than 22.1R2-S2, 22.1R3;
  *  22.2 versions earlier than 22.2R2-S1, 22.2R3.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Juniper Networks Junos OS&lt;/p&gt;
&lt;p&gt;An Improper Neutralization of Equivalent Special Elements vulnerability in the Packet Forwarding Engine (PFE) of Juniper Networks Junos OS on PTX Series allows a unauthenticated, adjacent attacker to cause a Denial of Service (DoS).&lt;/p&gt;
&lt;p&gt;When MPLS packets are meant to be sent to a flexible tunnel interface (FTI) and if the FTI tunnel is down, these will hit the reject NH, due to which the packets get sent to the CPU and cause a host path wedge condition. This will cause the FPC to hang and requires a manual restart to recover.&lt;/p&gt;
&lt;p&gt;Please note that this issue specifically affects PTX1000, PTX3000, PTX5000 with FPC3, PTX10002-60C, and PTX10008/16 with LC110x. Other PTX Series devices and Line Cards (LC) are not affected.&lt;/p&gt;
&lt;p&gt;The following log message can be seen when the issue occurs:&lt;/p&gt;
&lt;p&gt;Cmerror Op Set: Host Loopback: HOST LOOPBACK WEDGE DETECTED IN PATH ID &amp;lt;id&amp;gt; (URI: /fpc/&amp;lt;fpc&amp;gt;/pfe/&amp;lt;pfe&amp;gt;/cm/&amp;lt;cm&amp;gt;/Host_Loopback/&amp;lt;cm&amp;gt;/HOST_LOOPBACK_MAKE_CMERROR_ID[&amp;lt;id&amp;gt;])
This issue affects Juniper Networks Junos OS:&lt;/p&gt;
&lt;p&gt;*  All versions earlier than 20.4R3-S8;
  *  21.1 versions earlier than 21.1R3-S4;
  *  21.2 versions earlier than 21.2R3-S6;
  *  21.3 versions earlier than 21.3R3-S3;
  *  21.4 versions earlier than 21.4R3-S5;
  *  22.1 versions earlier than 22.1R2-S2, 22.1R3;
  *  22.2 versions earlier than 22.2R2-S1, 22.2R3.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2024-21600</guid>
    </item>
  </channel>
</rss>
