Junos OS: Mbuf leak due to processing MPLS packets in VPLS network.

Description

A Junos device with VPLS routing-instances configured on one or more interfaces may be susceptible to an mbuf leak when processing a specific MPLS packet. Approximately 1 mbuf is leaked per each packet processed. The number of mbufs is platform dependent. The following command provides the number of mbufs that are currently in use and maximum number of mbufs that can be allocated on a platform: > show system buffers 2437/3143/5580 mbufs in use (current/cache/total) Once the device runs out of mbufs it will become inaccessible and a restart will be required. This issue only affects end devices, transit devices are not affected. Affected releases are Juniper Networks Junos OS with VPLS configured running: 12.1X46 versions prior to 12.1X46-D76; 12.3X48 versions prior to 12.3X48-D66, 12.3X48-D70; 14.1 versions prior to 14.1R9; 14.1X53 versions prior to 14.1X53-D47; 14.2 versions prior to 14.2R8; 15.1 versions prior to 15.1F2-S19, 15.1F6-S10, 15.1R4-S9, 15.1R5-S7, 15.1R6-S4, 15.1R7; 15.1X49 versions prior to 15.1X49-D131, 15.1X49-D140; 15.1X53 versions prior to 15.1X53-D58 on EX2300/EX3400; 15.1X53 versions prior to 15.1X53-D233 on QFX5200/QFX5110; 15.1X53 versions prior to 15.1X53-D471 on NFX; 15.1X53 versions prior to 15.1X53-D66 on QFX10; 16.1 versions prior to 16.1R3-S8, 16.1R4-S6, 16.1R5; 16.2 versions prior to 16.2R1-S6, 16.2R2-S5, 16.2R3; 17.1 versions prior to 17.1R1-S7, 17.1R2-S6, 17.1R3; 17.2 versions prior to 17.2R1-S5, 17.2R2.

Scores

EPSS (exploitation in 30 days)

2.2% · top 17% of all CVEs (4 Nov 2026)

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.5.

Weakness

• denial of service
• CWE-400 (opens in a new tab)All about CWE-400 and its CVEs

Affected products

• Juniper Networks · Junos OS

  • affected 12.1X46 – < 12.1X46-D76
  • affected 12.3X48 – < 12.3X48-D66, 12.3X48-D70
  • affected 14.1 – < 14.1R9
  • affected 14.1X53 – < 14.1X53-D47
  • affected 14.2 – < 14.2R8
  • affected 15.1 – < 15.1F2-S19, 15.1F6-S10, 15.1R4-S9, 15.1R5-S7, 15.1R6-S4, 15.1R7
  • affected 15.1X49 – < 15.1X49-D131, 15.1X49-D140
  • affected 16.1 – < 16.1R3-S8, 16.1R4-S6, 16.1R5
  • affected 16.2 – < 16.2R1-S6, 16.2R2-S5, 16.2R3
  • affected 17.1 – < 17.1R1-S7, 17.1R2-S6, 17.1R3
  • affected 17.2 – < 17.2R1-S5, 17.2R2

• Juniper Networks · Junos OS

  • affected 15.1X53 – < 15.1X53-D58

• Juniper Networks · Junos OS

  • affected 15.1X53 – < 15.1X53-D233

• Juniper Networks · Junos OS

  • affected 15.1X53 – < 15.1X53-D471

• Juniper Networks · Junos OS

  • affected 15.1X53 – < 15.1X53-D66

What to do

Solution: The following software releases have been updated to resolve this specific issue: 12.1X46-D76, 12.3X48-D66, 12.3X48-D70, 14.1R9, 14.1X53-D47, 14.2R8, 15.1F2-S19, 15.1F6-S10, 15.1R4-S9, 15.1R5-S7, 15.1R6-S4, 15.1R7, 15.1X49-D131, 15.1X49-D140, 15.1X53-D233, 15.1X53-D471, 15.1X53-D58, 15.1X53-D66, 16.1R3-S8, 16.1R4-S6, 16.1R5, 16.2R1-S6, 16.2R2-S5, 16.2R3, 17.1R1-S7, 17.1R2-S6, 17.1R3, 17.2R1-S5, 17.2R2, 17.3R1 and all subsequent releases.

Workaround: There is no viable workaround for this issue.

Exploitation: Juniper SIRT is not aware of any malicious exploitation of this vulnerability.

References (3)

• 103740 (opens in a new tab)vdb-entryx_refsource_BIDx_transferred
• https://kb.juniper.net/JSA10855 (opens in a new tab)x_refsource_CONFIRMx_transferred
• 1040790 (opens in a new tab)vdb-entryx_refsource_SECTRACKx_transferred

Sources

The same CVE in the primary databases and aggregators, to check against.

• CVE.org record (opens in a new tab)
• CVE List JSON (GitHub) (opens in a new tab)
• NVD (opens in a new tab)
• FIRST EPSS (opens in a new tab)
• OSV.dev (opens in a new tab)
• GitHub Advisories (opens in a new tab)
• CIRCL Vulnerability-Lookup (opens in a new tab)

Badge for a README or a ticket

[![CVE-2018-0022](https://trackcve.app/badge/CVE-2018-0022.svg)](https://trackcve.app/cve/CVE-2018-0022)

Record last updated 16 Sept 2024, 19:11 UTC.