Junos OS: MX Series: The bbe-smgd process crashes if an unsupported configuration exists and a PPPoE client sends a specific message

Description

An Unchecked Error Condition vulnerability in the subscriber management daemon (smgd) of Juniper Networks Junos OS allows an unauthenticated adjacent attacker to cause a crash of and thereby a Denial of Service (DoS). In a subscriber management / broadband edge environment if a single session group configuration contains dual-stack and a pp0 interface, smgd will crash and restart every time a PPPoE client sends a specific message. This issue affects Juniper Networks Junos OS on MX Series: 16.1 version 16.1R1 and later versions prior to 18.4R3-S10; 19.1 versions prior to 19.1R2-S3, 19.1R3-S7; 19.2 versions prior to 19.2R1-S8, 19.2R3-S4; 19.3 versions prior to 19.3R3-S4; 19.4 versions prior to 19.4R3-S5; 20.1 versions prior to 20.1R3-S3; 20.2 versions prior to 20.2R3-S3; 20.3 versions prior to 20.3R3-S2; 20.4 versions prior to 20.4R3; 21.1 versions prior to 21.1R3; 21.2 versions prior to 21.2R2. This issue does not affect Juniper Networks Junos OS versions prior to 16.1R1.

Timeline

Scores

EPSS (exploitation in 30 days)

0.36% · top 70% of all CVEs (7 Nov 2026)

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

Weakness

• CWE-391 Unchecked Error Condition (opens in a new tab)All about CWE-391 and its CVEs
• Denial of Service (DoS)

Affected products

• Juniper Networks · Junos OS

  • affected unspecified – < 18.4R3-S10
  • unaffected unspecified – < 16.1R1
  • affected 16.1R1 – < 16.1*
  • affected 19.1 – < 19.1R2-S3, 19.1R3-S7
  • affected 19.2 – < 19.2R1-S8, 19.2R3-S4
  • affected 19.3 – < 19.3R3-S4
  • affected 19.4 – < 19.4R3-S5
  • affected 20.1 – < 20.1R3-S3
  • affected 20.2 – < 20.2R3-S3
  • affected 20.3 – < 20.3R3-S2
  • affected 20.4 – < 20.4R3
  • affected 21.1 – < 21.1R3
  • affected 21.2 – < 21.2R2

What to do

Solution: The following software releases have been updated to resolve this specific issue: 18.4R3-S10, 19.1R2-S3, 19.1R3-S7, 19.2R1-S8, 19.2R3-S4, 19.3R3-S4, 19.4R3-S5, 20.1R3-S3, 20.2R3-S3, 20.3R3-S2, 20.4R3, 21.1R3, 21.2R2, 21.3R1, and all subsequent releases.

Workaround: Remove the pp0 interface from a DHCPv6 dual-stack group and move to its own group with no dual-stack enabled. user@device# show system services dhcp-local-server dhcpv6 ... group <group-name1> { overrides { ... dual-stack <dual-stack-group-name>; } ... interface pp0.0; <<<<< delete and add to new group ... } group <group-name2> { <<<<< new group for PP0 interfaces to be handled separately. ... interface pp0.0; <<<<< ... }

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

References (1)

• https://kb.juniper.net/JSA11268 (opens in a new tab)x_refsource_CONFIRMx_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-2022-22160](https://trackcve.app/badge/CVE-2022-22160.svg)](https://trackcve.app/cve/CVE-2022-22160)

Record last updated 17 Sept 2024, 03:59 UTC.