A Missing Release of Memory after Effective Lifetime vulnerability in the routing protocol daemon (rpd) Juniper Networks Junos OS and Junos OS Evolved allows an unauthenticated attacker controlling an adjacent IS-IS neighbor to send a specific update packet causing a memory leak. Continued receipt and processing of these packets will exhaust all available memory, crashing rpd and creating a Denial of Service (DoS) condition.
Memory usage can be monitored through the use of the show task memory detail command. For example:
user@junos> show task memory detail | match ted-infra TED-INFRA-COOKIE 25 1072 28 1184 229
user@junos>
show task memory detail | match ted-infra TED-INFRA-COOKIE 31 1360 34 1472 307
This issue affects:
Junos OS:
- from 23.2 before 23.2R2,
- from 23.4 before 23.4R1-S2, 23.4R2,
- from 24.1 before 24.1R2;
Junos OS Evolved:
- from 23.2 before 23.2R2-EVO,
- from 23.4 before 23.4R1-S2-EVO, 23.4R2-EVO,
- from 24.1 before 24.1R2-EVO.
This issue does not affect Junos OS versions before 23.2R1 or Junos OS Evolved versions before 23.2R1-EVO.
Weakness
The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Junos | Juniper | 23.2 (including) | 23.2 (including) |
| Junos | Juniper | 23.2-r1 (including) | 23.2-r1 (including) |
| Junos | Juniper | 23.2-r1-s1 (including) | 23.2-r1-s1 (including) |
| Junos | Juniper | 23.2-r1-s2 (including) | 23.2-r1-s2 (including) |
| Junos | Juniper | 23.4 (including) | 23.4 (including) |
| Junos | Juniper | 23.4-r1 (including) | 23.4-r1 (including) |
| Junos | Juniper | 23.4-r1-s1 (including) | 23.4-r1-s1 (including) |
| Junos | Juniper | 23.4-r2 (including) | 23.4-r2 (including) |
| Junos | Juniper | 24.1 (including) | 24.1 (including) |
| Junos | Juniper | 24.1-r1 (including) | 24.1-r1 (including) |
| Junos_os_evolved | Juniper | 23.2 (including) | 23.2 (including) |
| Junos_os_evolved | Juniper | 23.2-r1 (including) | 23.2-r1 (including) |
| Junos_os_evolved | Juniper | 23.2-r1-s1 (including) | 23.2-r1-s1 (including) |
| Junos_os_evolved | Juniper | 23.2-r1-s2 (including) | 23.2-r1-s2 (including) |
| Junos_os_evolved | Juniper | 23.4 (including) | 23.4 (including) |
| Junos_os_evolved | Juniper | 23.4-r1 (including) | 23.4-r1 (including) |
| Junos_os_evolved | Juniper | 23.4-r1-s1 (including) | 23.4-r1-s1 (including) |
| Junos_os_evolved | Juniper | 23.4-r2 (including) | 23.4-r2 (including) |
| Junos_os_evolved | Juniper | 24.1 (including) | 24.1 (including) |
| Junos_os_evolved | Juniper | 24.1-r1 (including) | 24.1-r1 (including) |
Potential Mitigations
- Choose a language or tool that provides automatic memory management, or makes manual memory management less error-prone.
- For example, glibc in Linux provides protection against free of invalid pointers.
- When using Xcode to target OS X or iOS, enable automatic reference counting (ARC) [REF-391].
- To help correctly and consistently manage memory when programming in C++, consider using a smart pointer class such as std::auto_ptr (defined by ISO/IEC ISO/IEC 14882:2003), std::shared_ptr and std::unique_ptr (specified by an upcoming revision of the C++ standard, informally referred to as C++ 1x), or equivalent solutions such as Boost.