Firewall bypass via post-upgrade filter assignment race
Published Oct 19, 2021 · Updated Sep 17, 2024
Race condition in Junos OS on PTX1000 and PTX10002-60C systems allows remote attackers to bypass intended firewall filtering after an upgrade. The chassisd and dfwd processes race while applying interface configuration, causing filters to be omitted, substituted, or attached to the wrong logical or physical interface. The condition exists only after upgrading to an affected release, and misassigned filters let traffic that should be blocked propagate and disrupt services.
Summary
What happened
Race condition in Junos OS on PTX1000 and PTX10002-60C systems allows remote attackers to bypass intended firewall filtering after an upgrade. The chassisd and dfwd processes race while applying interface configuration, causing filters to be omitted, substituted, or attached to the wrong logical or physical interface. The condition exists only after upgrading to an affected release, and misassigned filters let traffic that should be blocked propagate and disrupt services.
The record
- CVE
- CVE-2021-31382
- Published
- Oct 19, 2021
- Updated
- Sep 17, 2024
- Vendor
- Juniper Networks
- Product
- Junos OS
- Classifications
- CWE-362
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 19, 2021CVE publishedPublication date reported by the CVE source.
- Sep 17, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=17.2R1 <17.2*
- Affected versionversion=17.3 <17.3R3-S12
- Affected versionversion=17.4 <17.4R3-S5
- Affected versionversion=18.1 <18.1R3-S13
- Affected versionversion=18.2 <18.2R3-S8
- Affected versionversion=18.3 <18.3R3-S5
- Affected versionversion=18.4 <18.4R1-S8, 18.4R2-S8, 18.4R3-S8
- Affected versionversion=18.4 <18.4R3-S9
- Affected versionversion=19.1 <19.1R3-S5
- Affected versionversion=19.1R1 <19.1*
- Affected versionversion=19.2 <19.2R3-S2
- Affected versionversion=19.3 <19.3R2-S6, 19.3R3-S3
- Affected versionversion=19.4 <19.4R2-S4, 19.4R3-S3
- Affected versionversion=19.4 <19.4R2-S5, 19.4R3-S5
- Affected versionversion=20.1 <20.1R3
- Affected versionversion=20.1 <20.1R3-S1
- Affected versionversion=20.2 <20.2R2-S3, 20.2R3
- Affected versionversion=20.2 <20.2R3-S2
- Affected versionversion=20.3 <20.3R2-S1, 20.3R3
- Affected versionversion=20.3 <20.3R3-S1
- Affected versionversion=20.4 <20.4R1-S1, 20.4R2
- Affected versionversion=20.4R1 <20.4*
- Affected versionversion=21.1 <21.1R2
- Affected versionversion=21.2R1 <21.2*
- Affected versionversion=21.3 <21.3R2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo