CVE-2021-0243

Junos OS: EX4300: Stateless firewall policer fails to discard traffic

MEDIUM
4.7
CVSS Score
Published: April 22, 2021 at 07:37 PM UTC
Updated: June 17, 2026 at 03:29 AM UTC
2 products affected across 2 vendorsJunosEx4300

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
MEDIUM4.7
Exploit prediction
EPSS 0.4%

Description

Improper Handling of Unexpected Data in the firewall policer of Juniper Networks Junos OS on EX4300 switches allows matching traffic to exceed set policer limits, possibly leading to a limited Denial of Service (DoS) condition. When the firewall policer discard action fails on a Layer 2 port, it will allow traffic to pass even though it exceeds set policer limits. Traffic will not get discarded, and will be forwarded even though a policer discard action is configured. When the issue occurs, traffic is not discarded as desired, which can be observed by comparing the Input bytes with the Output bytes using the following command: user@junos> monitor interface traffic Interface Link Input bytes (bps) Output bytes (bps) ge-0/0/0 Up 37425422 (82616) 37425354 (82616) <<<< egress ge-0/0/1 Up 37425898 (82616) 37425354 (82616) <<<< ingress The expected output, with input and output counters differing, is shown below: Interface Link Input bytes (bps) Output bytes (bps) ge-0/0/0 Up 342420570 (54600) 342422760 (54600) <<<< egress ge-0/0/1 Up 517672120 (84000) 342420570 (54600) <<<< ingress This issue only affects IPv4 policing. IPv6 traffic and firewall policing actions are not affected by this issue. This issue affects Juniper Networks Junos OS on the EX4300: All versions prior to 17.3R3-S10; 17.4 versions prior to 17.4R3-S3; 18.1 versions prior to 18.1R3-S11; 18.2 versions prior to 18.2R3-S6; 18.3 versions prior to 18.3R3-S4; 18.4 versions prior to 18.4R3-S6; 19.1 versions prior to 19.1R3-S3; 19.2 versions prior to 19.2R3-S1; 19.3 versions prior to 19.3R3-S1; 19.4 versions prior to 19.4R3; 20.1 versions prior to 20.1R2; 20.2 versions prior to 20.2R2.

Affected

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

v < 17.3R3-S1017.4 ≤ v < 17.4R3-S318.1 ≤ v < 18.1R3-S1118.2 ≤ v < 18.2R3-S618.3 ≤ v < 18.3R3-S418.4 ≤ v < 18.4R3-S619.1 ≤ v < 19.1R3-S319.2 ≤ v < 19.2R3-S119.3 ≤ v < 19.3R3-S119.4 ≤ v < 19.4R320.1 ≤ v < 20.1R220.2 ≤ v < 20.2R217.317.3 r117.3 r1-s117.3 r1-s417.3 r217.3 r2-s117.3 r2-s217.3 r2-s317.3 r2-s417.3 r2-s517.3 r317.3 r3-s117.3 r3-s217.3 r3-s317.3 r3-s417.3 r3-s517.3 r3-s617.3 r3-s717.3 r3-s817.3 r3-s917.417.4 r117.4 r1-s117.4 r1-s217.4 r1-s317.4 r1-s417.4 r1-s517.4 r1-s617.4 r1-s717.4 r217.4 r2-s117.4 r2-s1017.4 r2-s1117.4 r2-s1217.4 r2-s217.4 r2-s317.4 r2-s417.4 r2-s517.4 r2-s617.4 r2-s717.4 r2-s817.4 r2-s917.4 r317.4 r3-s117.4 r3-s218.118.1 r118.1 r218.1 r2-s118.1 r2-s218.1 r2-s418.1 r318.1 r3-s118.1 r3-s1018.1 r3-s218.1 r3-s318.1 r3-s418.1 r3-s518.1 r3-s618.1 r3-s718.1 r3-s818.1 r3-s918.218.2 r118.2 r1-s218.2 r1-s318.2 r1-s418.2 r1-s518.2 r218.2 r2-s118.2 r2-s218.2 r2-s318.2 r2-s418.2 r2-s518.2 r2-s618.2 r2-s718.2 r318.2 r3-s118.2 r3-s218.2 r3-s318.2 r3-s418.2 r3-s518.318.3 r118.3 r1-s118.3 r1-s218.3 r1-s318.3 r1-s418.3 r1-s518.3 r1-s618.3 r218.3 r2-s118.3 r2-s218.3 r2-s318.3 r2-s418.3 r318.3 r3-s118.3 r3-s218.3 r3-s318.418.4 r118.4 r1-s118.4 r1-s218.4 r1-s318.4 r1-s418.4 r1-s518.4 r1-s618.4 r1-s718.4 r218.4 r2-s118.4 r2-s218.4 r2-s318.4 r2-s418.4 r2-s518.4 r2-s618.4 r318.4 r3-s118.4 r3-s218.4 r3-s318.4 r3-s418.4 r3-s519.119.1 r119.1 r1-s119.1 r1-s219.1 r1-s319.1 r1-s419.1 r1-s519.1 r219.1 r2-s119.1 r319.1 r3-s119.1 r3-s219.219.2 r119.2 r1-s119.2 r1-s219.2 r1-s319.2 r1-s419.2 r1-s519.2 r219.2 r2-s119.2 r319.2 r3-s119.319.3 r119.3 r1-s119.3 r219.3 r2-s119.3 r2-s219.3 r2-s319.3 r2-s419.3 r2-s519.3 r319.419.4 r119.4 r1-s119.4 r1-s219.4 r219.4 r2-s119.4 r2-s220.120.1 r120.1 r1-s120.1 r1-s220.1 r1-s320.1 r1-s420.220.2 r120.2 r1-s120.2 r1-s220.2 r1-s3
Affected range stops below 17.3R3-S10, so it looks safe — our inference, not a vendor statement
Affected range stops below 17.4R3-S3, so it looks safe — our inference, not a vendor statement
Affected range stops below 18.1R3-S11, so it looks safe — our inference, not a vendor statement
Affected range stops below 18.2R3-S6, so it looks safe — our inference, not a vendor statement
Affected range stops below 18.3R3-S4, so it looks safe — our inference, not a vendor statement
Affected range stops below 18.4R3-S6, so it looks safe — our inference, not a vendor statement
Affected range stops below 19.1R3-S3, so it looks safe — our inference, not a vendor statement
Affected range stops below 19.2R3-S1, so it looks safe — our inference, not a vendor statement
Affected range stops below 19.3R3-S1, so it looks safe — our inference, not a vendor statement
Affected range stops below 19.4R3, so it looks safe — our inference, not a vendor statement
Affected range stops below 20.1R2, so it looks safe — our inference, not a vendor statement
Affected range stops below 20.2R2, so it looks safe — our inference, not a vendor statement
juniper-ex4300 (environment)
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

References (1)

x_refsource_MISCVendor Advisory
https://kb.juniper.net/JSA11136

CVSS

4.7MEDIUMjuniper
Attack Vector
ADJACENT_NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
CHANGED
Confidentiality
NONE
Integrity
NONE
Availability
LOW
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-241NVD-CWE-Other

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