title: Junos OS and Junos OS Evolved: An l2cpd memory leak can occur when specific LLDP packets are received leading to a DoS
description: A Missing Release of Memory after Effective Lifetime vulnerability in the Layer-2 control protocols daemon (l2cpd) of Juniper Networks Junos OS and Junos OS Evolved allows an unauthenticated adjacent attacker to cause a memory leak. Continued exploitation can lead to memory exhaustion and thereby a Denial of Service (DoS). This issue occurs when specific LLDP packets are received. The impact of the l2cpd cores is that if any of the stp protocols (rstp, mstp or vstp) is used then stp re-converges and traffic loss will occur during that time. Also if any services depend on LLDP state (like PoE or VoIP device recognition) then these will also be affected. The memory utilization of the L2CPd process can be monitored with the following command: user@host> show system processes extensive | match l2cpd 1234 root 52 0 521M 43412K RUN 1 4:02 34.47% l2cpd This issue affects: Juniper Networks Junos OS 18.4 version 18.4R2-S4 and later versions prior to 18.4R2-S10. 19.2 versions prior to 19.2R1-S8, 19.2R3-S4; 19.3 versions prior to 19.3R3-S5; 19.4 versions prior to 19.4R3-S7; 20.1 versions prior to 20.1R3-S3; 20.2 versions prior to 20.2R3-S2; 20.3 versions prior to 20.3R3-S1; 20.4 versions prior to 20.4R3; 21.1 versions prior to 21.1R2-S2, 21.1R3; 21.2 versions prior to 21.2R2; Juniper Networks Junos OS Evolved All versions prior to 20.4R3-S2-EVO; 21.1 version 21.1R1-EVO and later versions; 21.2 versions prior to 21.2R2-EVO. This issue does not affect: Juniper Networks Junos OS 19.1 version 19.1R1 and later versions.
problem types: CWE-401 Missing Release of Memory after Effective Lifetime
affected:
{
product: Junos OS
vendor: Juniper Networks
versions:
lessThan: 18.4R2-S4, status: unaffected, version: unspecified, versionType: custom
changes: [at: 18.4R2-S10, status: unaffected], lessThan: 18.4*, status: affected, version: 18.4R2-S4, versionType: custom
lessThan: 19.1*, status: unaffected, version: 19.1R1, versionType: custom
lessThan: 19.2R1-S8, 19.2R3-S4, status: affected, version: 19.2, versionType: custom
lessThan: 19.3R3-S5, status: affected, version: 19.3, versionType: custom
lessThan: 19.4R3-S7, status: affected, version: 19.4, versionType: custom
lessThan: 20.1R3-S3, status: affected, version: 20.1, versionType: custom
lessThan: 20.2R3-S2, status: affected, version: 20.2, versionType: custom
lessThan: 20.3R3-S1, status: affected, version: 20.3, versionType: custom
lessThan: 20.4R3, status: affected, version: 20.4, versionType: custom
lessThan: 21.1R2-S2, 21.1R3, status: affected, version: 21.1, versionType: custom
lessThan: 21.2R2, status: affected, version: 21.2, versionType: custom
}
{
product: Junos OS Evolved
vendor: Juniper Networks
versions:
lessThan: 20.4R3-S2-EVO, status: affected, version: unspecified, versionType: custom
lessThan: 21.1*, status: affected, version: 21.1R1-EVO, versionType: custom
lessThan: 21.2R2-EVO, status: affected, version: 21.2, versionType: custom
}
metrics:
cvssV3_1: [
attackComplexity: LOW
attackVector: ADJACENT_NETWORK
availabilityImpact: HIGH
baseScore: 6.5
baseSeverity: MEDIUM
confidentialityImpact: NONE
integrityImpact: NONE
privilegesRequired: NONE
scope: UNCHANGED
userInteraction: NONE
vectorString: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
version: 3.1
]
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:
for Junos OS: 19.2R1-S8, 19.2R3-S4, 19.3R3-S5, 19.4R3-S7, 20.1R3-S3, 20.2R3-S2, 20.3R3-S1, 20.4R3, 21.1R2-S2, 21.1R3, 21.2R2, 21.3R1, and all subsequent releases.
for Junos OS Evolved: 20.4R3-S2-EVO, 21.2R2-EVO, 21.3R1-EVO, and all subsequent releases.
workarounds: There are no viable workarounds for this issue.