CVE-2023-36833

Junos OS Evolved: PTX10001-36MR, and PTX10004, PTX10008, PTX10016 with LC1201/1202: The aftman-bt process will crash in a MoFRR scenario after multiple link flaps

MEDIUM
6.5
CVSS Score
Published: July 14, 2023 at 04:56 PM UTC
Updated: June 17, 2026 at 06:07 AM UTC
6 products affected across 2 vendorsJunos OS EvolvedPtx10008Ptx10004

Using Junos OS Evolved by Juniper Networks?

Get instant alerts when new vulnerabilities affect Junos OS Evolved - 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

A Use After Free vulnerability in the packet forwarding engine (PFE) of Juniper Networks Junos OS Evolved on PTX10001-36MR, and PTX10004, PTX10008, PTX10016 with LC1201/1202 allows an adjacent, unauthenticated attacker to cause a Denial of Service (DoS). The process 'aftman-bt' will crash after multiple flaps on a multicast-only fast reroute (MoFRR) enabled interface. This will cause the respective FPC to stop forwarding traffic and it needs to be rebooted to restore the service. An indication that the system experienced this issue is the following log message: <date> <hostname> evo-aftmand-bt[<pid>]: [Error] jexpr_fdb: sanity check failed, ... , app_name L3 Mcast Routes This issue affects Juniper Networks Junos OS Evolved on PTX10001-36MR, PTX10004, PTX10008, PTX10016 with LC1201/1202: 21.2 version 21.2R1-EVO and later versions; 21.3 version 21.3R1-EVO and later versions; 21.4 versions prior to 21.4R3-S3-EVO; 22.1 version 22.1R1-EVO and later versions; 22.2 versions prior to 22.2R3-S2-EVO; 22.3 versions prior to 22.3R3-EVO; 22.4 versions prior to 22.4R1-S2-EVO, 22.4R2-EVO.

Affected

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

21.2 ≤ v < 21.2*21.3 ≤ v < 21.3*21.4 ≤ v < 21.4R3-S3-EVO22.1 ≤ v < 22.1*22.2 ≤ v < 22.2R3-S2-EVO22.3 ≤ v < 22.3R3-EVO22.4 ≤ v < 22.4R1-S2-EVO, 22.4R2-EVO21.221.321.422.122.222.322.4
Affected range stops below 21.2*, so it looks safe — our inference, not a vendor statement
Affected range stops below 21.3*, so it looks safe — our inference, not a vendor statement
Affected range stops below 21.4R3-S3-EVO, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.1*, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.2R3-S2-EVO, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.3R3-EVO, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.4R1-S2-EVO, 22.4R2-EVO, so it looks safe — our inference, not a vendor statement
All versions
All versions
All versions
All versions

Remediation

No guide yet

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

Patch and advisory references

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-416

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