First published: Thu Jan 12 2023(Updated: )
An Improper Preservation of Consistency Between Independent Representations of Shared State vulnerability in the Packet Forwarding Engine (PFE) of Juniper Networks Junos OS allows an adjacent, unauthenticated attacker to cause a Denial of Service (DoS) to device due to out of resources. When a device is configured with "service-provider/SP style" switching, and mac-limiting is configured on an Aggregated Ethernet (ae) interface, and then a PFE is restarted or the device is rebooted, mac-limiting doesn't work anymore. Please note that the issue might not be apparent as traffic will continue to flow through the device although the mac table and respective logs will indicate that mac limit is reached. Functionality can be restored by removing and re-adding the MAC limit configuration. This issue affects Juniper Networks Junos OS on QFX5k Series, EX46xx Series: All versions prior to 20.2R3-S5; 20.3 versions prior to 20.3R3-S5; 20.4 versions prior to 20.4R3-S4; 21.1 versions prior to 21.1R3-S3; 21.2 versions prior to 21.2R3-S1; 21.3 versions prior to 21.3R3 on; 21.4 versions prior to 21.4R3 on; 22.1 versions prior to 22.1R2 on.
Credit: sirt@juniper.net
Affected Software | Affected Version | How to fix |
---|---|---|
Juniper JUNOS | <20.2 | |
Juniper JUNOS | =20.2 | |
Juniper JUNOS | =20.2-r1 | |
Juniper JUNOS | =20.2-r1-s1 | |
Juniper JUNOS | =20.2-r1-s2 | |
Juniper JUNOS | =20.2-r1-s3 | |
Juniper JUNOS | =20.2-r2 | |
Juniper JUNOS | =20.2-r2-s1 | |
Juniper JUNOS | =20.2-r2-s2 | |
Juniper JUNOS | =20.2-r2-s3 | |
Juniper JUNOS | =20.2-r3 | |
Juniper JUNOS | =20.2-r3-s1 | |
Juniper JUNOS | =20.2-r3-s2 | |
Juniper JUNOS | =20.2-r3-s3 | |
Juniper JUNOS | =20.2-r3-s4 | |
Juniper JUNOS | =20.3 | |
Juniper JUNOS | =20.3-r1 | |
Juniper JUNOS | =20.3-r1-s1 | |
Juniper JUNOS | =20.3-r1-s2 | |
Juniper JUNOS | =20.3-r2 | |
Juniper JUNOS | =20.3-r2-s1 | |
Juniper JUNOS | =20.3-r3 | |
Juniper JUNOS | =20.3-r3-s1 | |
Juniper JUNOS | =20.3-r3-s2 | |
Juniper JUNOS | =20.3-r3-s3 | |
Juniper JUNOS | =20.3-r3-s4 | |
Juniper JUNOS | =20.4 | |
Juniper JUNOS | =20.4-r1 | |
Juniper JUNOS | =20.4-r1-s1 | |
Juniper JUNOS | =20.4-r2 | |
Juniper JUNOS | =20.4-r2-s1 | |
Juniper JUNOS | =20.4-r2-s2 | |
Juniper JUNOS | =20.4-r3 | |
Juniper JUNOS | =20.4-r3-s1 | |
Juniper JUNOS | =20.4-r3-s2 | |
Juniper JUNOS | =20.4-r3-s3 | |
Juniper JUNOS | =21.1 | |
Juniper JUNOS | =21.1-r1 | |
Juniper JUNOS | =21.1-r1-s1 | |
Juniper JUNOS | =21.1-r2 | |
Juniper JUNOS | =21.1-r2-s1 | |
Juniper JUNOS | =21.1-r2-s2 | |
Juniper JUNOS | =21.1-r3 | |
Juniper JUNOS | =21.1-r3-s1 | |
Juniper JUNOS | =21.1-r3-s2 | |
Juniper JUNOS | =21.2 | |
Juniper JUNOS | =21.2-r1 | |
Juniper JUNOS | =21.2-r1-s1 | |
Juniper JUNOS | =21.2-r1-s2 | |
Juniper JUNOS | =21.2-r2 | |
Juniper JUNOS | =21.2-r2-s1 | |
Juniper JUNOS | =21.2-r2-s2 | |
Juniper JUNOS | =21.2-r3 | |
Juniper JUNOS | =21.3 | |
Juniper JUNOS | =21.3-r1 | |
Juniper JUNOS | =21.3-r1-s1 | |
Juniper JUNOS | =21.3-r1-s2 | |
Juniper JUNOS | =21.3-r2 | |
Juniper JUNOS | =21.3-r2-s1 | |
Juniper JUNOS | =21.3-r2-s2 | |
Juniper JUNOS | =21.4 | |
Juniper JUNOS | =21.4-r1 | |
Juniper JUNOS | =21.4-r1-s1 | |
Juniper JUNOS | =21.4-r1-s2 | |
Juniper JUNOS | =21.4-r2 | |
Juniper JUNOS | =22.1-r1 | |
Juniper JUNOS | =22.1-r1-s1 | |
Juniper EX4600 | ||
Juniper Ex4600-vc | ||
Juniper Ex4650 | ||
Juniper Qfx5100 | ||
Juniper Qfx5100-96s | ||
Juniper Qfx5110 | ||
Juniper Qfx5120 | ||
Juniper Qfx5130 | ||
Juniper Qfx5200 | ||
Juniper Qfx5200-32c | ||
Juniper Qfx5200-48y | ||
Juniper Qfx5210 | ||
Juniper Qfx5210-64c | ||
Juniper Qfx5220 |
The following software releases have been updated to resolve this specific issue: 20.2R3-S5, 20.3R3-S5, 20.4R3-S4, 21.1R3-S3, 21.2R3-S1, 21.3R3, 21.4R3, 22.1R2, 22.2R1, and all subsequent releases.
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.