Junos OS and Junos OS Evolved: In an EVPN-MPLS scenario churn of ESI routes causes a memory leak in l2ald
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 23.2R2-S3-EVO, 23.4R2-S4-EVO, 24.2R2-EVO and 5 more.
A Missing Release of Memory after Effective Lifetime vulnerability in the Layer 2 Address Learning Daemon (l2ald) of Juniper Networks Junos OS and Junos OS Evolved allows an adjacent, unauthenticated attacker to cause a memory leak ultimately leading to a Denial of Service (DoS). In an EVPN-MPLS scenario, routes learned from remote multi-homed Provider Edge (PE) devices are programmed as ESI routes. Due to a logic issue in the l2ald memory management, memory allocated for these routes is not released when there is churn for these routes. As a result, memory leaks in the l2ald process which will ultimately lead to a crash and restart of l2ald. Use the following command to monitor the memory consumption by l2ald: user@device> show system process extensive | match "PID|l2ald" This issue affects: Junos OS: * all versions before 22.4R3-S5, * 23.2 versions before 23.2R2-S3, * 23.4 versions before 23.4R2-S4, * 24.2 versions before 24.2R2; Junos OS Evolved: * all versions before 22.4R3-S5-EVO, * 23.2 versions before 23.2R2-S3-EVO, * 23.4 versions before 23.4R2-S4-EVO, * 24.2 versions before 24.2R2-EVO.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Juniper Networks | >=23.2 <23.2R2-S3-EVO, >=23.4 <23.4R2-S4-EVO, >=24.2 <24.2R2-EVO, >=all version prior to <22.4R3-S5-EVO, <22.4R3-S5, >=23.2 <23.2R2-S3, >=23.4 <23.4R2-S4, >=24.2 <24.2R2 | 23.2R2-S3-EVO, 23.4R2-S4-EVO, 24.2R2-EVO, 22.4R3-S5-EVO, 22.4R3-S5, 23.2R2-S3, 23.4R2-S4, 24.2R2 |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket