CVE-2023-44178

A Stack-based Buffer Overflow vulnerability in the CLI command of Juniper Networks Junos OS allows a low privileged attacker to execute a specific CLI commands leading to Denial of Service.

Repeated actions by the attacker will create a sustained Denial of Service (DoS) condition.

This issue affects Juniper Networks:

Junos OS

• All versions prior to 19.1R3-S10;
• 19.2 versions prior to 19.2R3-S7;
• 19.3 versions prior to 19.3R3-S8;
• 19.4 versions prior to 19.4R3-S12;
• 20.2 versions prior to 20.2R3-S8;
• 20.4 versions prior to 20.4R3-S8;
• 21.2 versions prior to 21.2R3-S6;
• 21.3 versions prior to 21.3R3-S5;
• 21.4 versions prior to 21.4R3-S5;
• 22.1 versions prior to 22.1R3-S3;
• 22.2 versions prior to 22.2R3-S2;
• 22.3 versions prior to 22.3R3-S1;
• 22.4 versions prior to 22.4R2-S1;
• 23.2 versions prior to 23.2R2.

Weakness

A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function).

Affected Software

Potential Mitigations

• Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking.
• D3-SFCV (Stack Frame Canary Validation) from D3FEND [REF-1334] discusses canary-based detection in detail.
• Run or compile the software using features or extensions that randomly arrange the positions of a program’s executable and libraries in memory. Because this makes the addresses unpredictable, it can prevent an attacker from reliably jumping to exploitable code.
• Examples include Address Space Layout Randomization (ASLR) [REF-58] [REF-60] and Position-Independent Executables (PIE) [REF-64]. Imported modules may be similarly realigned if their default memory addresses conflict with other modules, in a process known as “rebasing” (for Windows) and “prelinking” (for Linux) [REF-1332] using randomly generated addresses. ASLR for libraries cannot be used in conjunction with prelink since it would require relocating the libraries at run-time, defeating the whole purpose of prelinking.
• For more information on these techniques see D3-SAOR (Segment Address Offset Randomization) from D3FEND [REF-1335].

References

• https://supportportal.juniper.net/JSA73140
• https://supportportal.juniper.net/JSA73140