title: Junos OS and Junos OS Evolved: Stack overflow vulnerability in CLI command processing
description:
A Stack-based Buffer Overflow vulnerability in the CLI command of Juniper Networks Junos and Junos EVO 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-S4;
*  22.1 versions prior to 22.1R3-S3;
*  22.2 versions prior to 22.2R3-S1;
*  22.3 versions prior to 22.3R3;
*  22.4 versions prior to 22.4R2.
Junos OS Evolved:
*  All versions prior to 20.4R3-S8-EVO;
*  21.2 versions prior to 21.2R3-S6-EVO;
*  21.3 versions prior to 21.3R3-S5-EVO;
*  21.4 versions prior to 21.4R3-S4-EVO;
*  22.1 versions prior to 22.1R3-S3-EVO;
*  22.2 versions prior to 22.2R3-S1-EVO;
*  22.3 versions prior to 22.3R3-EVO;
*  22.4 versions prior to 22.4R2-EVO.
problem types: CWE-787 Out-of-bounds Write
affected:
{
defaultStatus: unaffected
product: Junos OS
vendor: Juniper Networks
versions:
lessThan: 19.1R3-S10, status: affected, version: 0, versionType: semver
lessThan: 19.2R3-S7, status: affected, version: 19.2, versionType: semver
lessThan: 19.3R3-S8, status: affected, version: 19.3, versionType: semver
lessThan: 19.4R3-S12, status: affected, version: 19.4, versionType: semver
lessThan: 20.2R3-S8, status: affected, version: 20.2, versionType: semver
lessThan: 20.4R3-S8, status: affected, version: 20.4, versionType: semver
lessThan: 21.2R3-S6, status: affected, version: 21.2, versionType: semver
lessThan: 21.3R3-S5, status: affected, version: 21.3, versionType: semver
lessThan: 21.4R3-S4, status: affected, version: 21.4, versionType: semver
lessThan: 22.1R3-S3, status: affected, version: 22.1, versionType: semver
lessThan: 22.2R3-S1, status: affected, version: 22.2, versionType: semver
lessThan: 22.3R3, status: affected, version: 22.3, versionType: semver
lessThan: 22.4R2, status: affected, version: 22.4, versionType: semver
}
{
defaultStatus: unaffected
product: Junos OS Evolved
vendor: Juniper Networks
versions:
lessThan: 20.4R3-S8-EVO, status: affected, version: 0, versionType: semver
lessThan: 21.2R3-S6-EVO, status: affected, version: 21.2, versionType: semver
lessThan: 21.3R3-S5-EVO, status: affected, version: 21.3, versionType: semver
lessThan: 21.4R3-S4-EVO, status: affected, version: 21.4, versionType: semver
lessThan: 22.1R3-S3-EVO, status: affected, version: 22.1, versionType: semver
lessThan: 22.2R3-S1-EVO, status: affected, version: 22.2, versionType: semver
lessThan: 22.3R3-EVO, status: affected, version: 22.3, versionType: semver
lessThan: 22.4R2-EVO, status: affected, version: 22.4, versionType: semver
}
metrics:
cvssV3_1: [
attackComplexity: LOW
attackVector: LOCAL
availabilityImpact: HIGH
baseScore: 5.5
baseSeverity: MEDIUM
confidentialityImpact: NONE
integrityImpact: NONE
privilegesRequired: LOW
scope: UNCHANGED
userInteraction: NONE
vectorString: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
version: 3.1
]
format: CVSS
scenarios: GENERAL
exploits: Juniper SIRT is not aware of any malicious exploitation of this vulnerability.
solutions: The following software releases have been updated to resolve this specific issue:
Junos OS: 19.1R3-S10, 19.2R3-S7, 19.3R3-S8, 19.4R3-S12, 20.2R3-S8, 20.4R3-S8, 21.2R3-S5, 21.2R3-S6, 21.3R3-S5, 21.4R3-S4, 22.1R3-S3, 22.2R3-S1, 22.3R3, 22.4R2, 22.4R3, 23.2R1, and all subsequent releases.
Junos OS Evolved: 20.4R3-S8-EVO, 21.2R3-S6-EVO, 21.3R3-S5-EVO, 21.4R3-S4-EVO, 22.1R3-S3-EVO, 22.2R3-S1-EVO, 22.3R3-EVO, 22.4R2-EVO, 22.4R3-EVO, 23.2R1-EVO, and all subsequent releases.
workarounds: To reduce the risk of malicious exploitation use access lists or firewall filters to limit access to the CLI only from trusted hosts and administrators.
There are no known workarounds for this issue.