CVE-2023-36839: Junos OS and Junos OS Evolved: An l2cpd crash will occur when specific LLDP packets are received
Noroxi assessment
Priority: Monitor (action score 26/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.30% (FIRST EPSS).
- Someone on the same network segment can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Juniper Networks Junos OS 20.4R3-S8, 21.1*, 21.2R3-S5; Juniper Networks Junos OS Evolved 20.4R3-S8-EVO, 21.1*-EVO, 21.2R3-S5-EVO.
Low priority for now. Upgrade to Juniper Networks Junos OS 20.4R3-S8, 21.1*, 21.2R3-S5; Juniper Networks Junos OS Evolved 20.4R3-S8-EVO, 21.1*-EVO, 21.2R3-S5-EVO or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
An Improper Validation of Specified Quantity in Input vulnerability in the Layer-2 control protocols daemon (l2cpd) of Juniper Networks Junos OS and Junos OS Evolved allows an unauthenticated adjacent attacker who sends specific LLDP packets to cause a Denial of Service(DoS). This issue occurs when specific LLDP packets are received and telemetry polling is being done on the device. 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. This issue affects: Juniper Networks Junos OS * All versions prior to 20.4R3-S8; * 21.1 version 21.1R1 and later versions; * 21.2 versions prior to 21.2R3-S5; * 21.3 versions prior to 21.3R3-S4; * 21.4 versions prior to 21.4R3-S3; * 22.1 versions prior to 22.1R3-S2; * 22.2 versions prior to 22.2R3; * 22.3 versions prior to 22.3R2-S2; * 22.4 versions prior to 22.4R2; Juniper Networks Junos OS Evolved * All versions prior to 20.4R3-S8-EVO; * 21.1 version 21.1R1-EVO and later versions; * 21.2 versions prior to 21.2R3-S5-EVO; * 21.3 versions prior to 21.3R3-S4-EVO; * 21.4 versions prior to 21.4R3-S3-EVO; * 22.1 versions prior to 22.1R3-S2-EVO; * 22.2 versions prior to 22.2R3-EVO; * 22.3 versions prior to 22.3R2-S2-EVO; * 22.4 versions prior to 22.4R1-S1-EVO;
- Published
- Oct 12, 2023
- Updated
- Jun 17, 2026
- EPSS
- 0.3% · 23th percentile
- CWE
- CWE-1284
Report tools
Action score
26
Monitor
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 6.5
- CNA · juniper
- 6.5
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| juniper | junos | cpe:2.3:o:juniper:junos |
| juniper | junos os evolved | cpe:2.3:o:juniper:junos_os_evolved |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- juniper junosbefore 20.4
- juniper junos20.4
- juniper junos21.1
- juniper junos21.2
- juniper junos21.3
- juniper junos21.4
- juniper junos22.1
- juniper junos22.2
- juniper junos22.3
- juniper junos22.4
- juniper junos os evolvedbefore 20.4
- juniper junos os evolved20.4
- juniper junos os evolved21.1
- juniper junos os evolved21.2
- juniper junos os evolved21.3
- juniper junos os evolved21.4
- juniper junos os evolved22.1
- juniper junos os evolved22.2
- juniper junos os evolved22.3
- juniper junos os evolved22.4
Versions reported by the vendor
Affected version ranges reported by the assigning authority (juniper). Independent of NVD's CPE analysis and usually ahead of it.
Juniper Networks Junos OS
- before 20.4R3-S8affected · semver
- 21.1R1 and later · before 21.1*affected · semver
- 21.2 and later · before 21.2R3-S5affected · semver
- 21.3 and later · before 21.3R3-S4affected · semver
- 21.4 and later · before 21.4R3-S3affected · semver
- 22.1 and later · before 22.1R3-S2affected · semver
- 22.2 and later · before 22.2R3affected · semver
- 22.3 and later · before 22.3R2-S2, 22.3R3affected · semver
- 22.4 and later · before 22.4R2affected · semver
Juniper Networks Junos OS Evolved
- before 20.4R3-S8-EVOaffected · semver
- 21.1R1-EVO and later · before 21.1*-EVOaffected · semver
- 21.2-EVO and later · before 21.2R3-S5-EVOaffected · semver
- 21.3-EVO and later · before 21.3R3-S4-EVOaffected · semver
- 21.4-EVO and later · before 21.4R3-S3-EVOaffected · semver
- 22.1-EVO and later · before 22.1R3-S2-EVOaffected · semver
- 22.2-EVO and later · before 22.2R3-EVOaffected · semver
- 22.3-EVO and later · before 22.3R2-S2-EVO, 22.3R3-EVOaffected · semver
- 22.4-EVO and later · before 22.4R1-S1-EVO, 22.4R2-EVOaffected · semver
Same product
juniper: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-36845Junos OS: EX and SRX Series: A PHP vulnerability in J-Web allows an unauthenticated to control an important environment variableKEV98Now
- CVE-2023-36846Junos OS: SRX Series: A vulnerability in J-Web allows an unauthenticated attacker to upload arbitrary filesKEV79This week
- CVE-2023-36844Junos OS: EX Series: A PHP vulnerability in J-Web allows an unauthenticated attacker to control important environment variablesKEV78This week
Published before and after this one in the same product
- ← EarlierCVE-2023-44188Oct 11, 2023 · Junos OS: jkdsd crash due to multiple telemetry requests21Monitor
- ← EarlierCVE-2023-22392Oct 12, 2023 · Junos OS: PTX Series and QFX10000 Series: Received flow-routes which aren't installed as the hardware doesn't support them, lead to an FPC heap memory leak26Monitor
- Later →CVE-2023-36841Oct 12, 2023 · Junos OS: MX Series: Receipt of malformed TCP traffic will cause a Denial of Service30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Juniper Networks Junos OS | 20.4R3-S8 | Vendor (CNA) |
| Juniper Networks Junos OS | 21.1* | Vendor (CNA) |
| Juniper Networks Junos OS | 21.2R3-S5 | Vendor (CNA) |
| Juniper Networks Junos OS | 21.3R3-S4 | Vendor (CNA) |
| Juniper Networks Junos OS | 21.4R3-S3 | Vendor (CNA) |
| Juniper Networks Junos OS | 22.1R3-S2 | Vendor (CNA) |
| Juniper Networks Junos OS | 22.2R3 | Vendor (CNA) |
| Juniper Networks Junos OS | 22.3R2-S2, 22.3R3 | Vendor (CNA) |
| Juniper Networks Junos OS | 22.4R2 | Vendor (CNA) |
| Juniper Networks Junos OS Evolved | 20.4R3-S8-EVO | Vendor (CNA) |
| Juniper Networks Junos OS Evolved | 21.1*-EVO | Vendor (CNA) |
| Juniper Networks Junos OS Evolved | 21.2R3-S5-EVO | Vendor (CNA) |
| Juniper Networks Junos OS Evolved | 21.3R3-S4-EVO | Vendor (CNA) |
| Juniper Networks Junos OS Evolved | 21.4R3-S3-EVO | Vendor (CNA) |
| Juniper Networks Junos OS Evolved | 22.1R3-S2-EVO | Vendor (CNA) |
| Juniper Networks Junos OS Evolved | 22.2R3-EVO | Vendor (CNA) |
| Juniper Networks Junos OS Evolved | 22.3R2-S2-EVO, 22.3R3-EVO | Vendor (CNA) |
| Juniper Networks Junos OS Evolved | 22.4R1-S1-EVO, 22.4R2-EVO | Vendor (CNA) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone on the same network segment can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Adjacent
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-1284 · Improper Validation of Specified Quantity in InputCVSS vector
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.