Product Affected

This issue affects all versions of Junos OS. Affected platforms: MX Series.
Medium

Problem

A Missing Release of Memory after Effective Lifetime vulnerability in the BroadBand Edge subscriber management daemon (bbe-smgd) of Juniper Networks Junos OS on MX Series allows an adjacent, unauthenticated attacker to cause a Denial of Service (DoS).

If the authentication packet-type option is configured and a received packet does not match that packet type, the memory leak occurs. When all memory available to bbe-smgd has been consumed, no new subscribers will be able to login.

The memory utilization of bbe-smgd can be monitored with the following show command:

user@host> show system processes extensive | match bbe-smgd

The below log message can be observed when this limit has been reached:

bbesmgd[<PID>]: %DAEMON-3-SMD_DPROF_RSMON_ERROR: Resource unavailability, Reason: Daemon Heap Memory exhaustion


This issue affects Junos OS on MX Series:

  • all versions before 22.4R3-S8,
  • 23.2 versions before 23.2R2-S5,
  • 23.4 versions before 23.4R2-S6,
  • 24.2 versions before 24.2R2-S2,
  • 24.4 versions before 24.4R2,
  • 25.2 versions before 25.2R2.

 

A system is only affected, when packet-types is configured as follows:

[ interface <interface> auto-configure (stacked-)vlan-ranges dynamic-profile <profile-name> accept <packet-type1> ]

which allows packets of type 1 to be processed on receipt, but

[ interfaces <interface>auto-configure (stacked-)vlan-ranges authentication packet-types <packet-type2> ]

is a mismatch and doesn't require authentication for these packets.

 

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

 

This issue was seen during production usage.

Solution

The following software releases have been updated to resolve this specific issue: 22.4R3-S8, 23.2R2-S5, 23.4R2-S6, 24.2R2-S2, 24.4R2, 25.2R2, 25.4R1, and all subsequent releases.

 

This issue is being tracked as 1853434 which is visible on the Customer Support website.

 

Note: Juniper SIRT's policy is not to evaluate releases which are beyond End of Engineering (EOE) or End of Life (EOL).

Workaround

There are no known workarounds for this issue. 

Severity Assessment

Information for how Juniper Networks uses CVSS can be found at KB 16446 [juniper.net] "Common Vulnerability Scoring System (CVSS) and Juniper's Security Advisories."

Modification History

2026-04-08: Initial Publication

Related Information