CVE-2023-36849

Junos OS and Junos OS Evolved: The l2cpd will crash when a malformed LLDP packet is received

MEDIUM
6.5
CVSS Score
Published: July 14, 2023 at 05:58 PM UTC
Updated: June 17, 2026 at 06:07 AM UTC
3 products affected across 2 vendorsJunosJunos OS EvolvedJunos OS Evolved

Using Junos OS by Juniper Networks?

Get instant alerts when new vulnerabilities affect Junos OS - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM6.5
Exploit prediction
EPSS 0.3%
SSVC
No known exploit

Description

An Improper Check or Handling of Exceptional Conditions 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 Denial of Service (DoS). When a malformed LLDP packet is received, l2cpd will crash and restart. The impact of the l2cpd crash is reinitialization of STP protocols (RSTP, MSTP or VSTP), and MVRP and ERP. Also, if any services depend on LLDP state (like PoE or VoIP device recognition), then these will also be affected. Continued receipt of such packets will lead to a sustained Denial of Service. This issue affects: Juniper Networks Junos OS 21.4 versions prior to 21.4R3-S3; 22.1 versions prior to 22.1R3-S3; 22.2 versions prior to 22.2R2-S1, 22.2R3; 22.3 versions prior to 22.3R2. Juniper Networks Junos OS Evolved 21.4-EVO versions prior to 21.4R3-S2-EVO; 22.1-EVO versions prior to 22.1R3-S3-EVO; 22.2-EVO versions prior to 22.2R2-S1-EVO, 22.2R3-EVO; 22.3-EVO versions prior to 22.3R2-EVO.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Affected range stops below 21.4R3-S3, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.1R3-S3, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.2R2-S1, 22.2R3, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.3R2, so it looks safe — our inference, not a vendor statement
21.4 ≤ v < 21.4R3-S2-EVO22.1 ≤ v < 22.1R3-S3-EVO22.2 ≤ v < 22.2R2-S1-EVO, 22.2R3-EVO22.3 ≤ v < 22.3R2-EVO21.422.122.222.3
Affected range stops below 21.4R3-S2-EVO, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.1R3-S3-EVO, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.2R2-S1-EVO, 22.2R3-EVO, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.3R2-EVO, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

References (1)

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

6.5MEDIUMjuniper
Attack Vector
ADJACENT_NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-703

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card