Project Subscriptions
| Vendors | Products |
|---|---|
|
Juniper
Subscribe
|
Junos
Subscribe
Srx100
Subscribe
Srx110
Subscribe
Srx1400
Subscribe
Srx1500
Subscribe
Srx210
Subscribe
Srx220
Subscribe
Srx240
Subscribe
Srx240h2
Subscribe
Srx300
Subscribe
Srx320
Subscribe
Srx340
Subscribe
Srx3400
Subscribe
Srx345
Subscribe
Srx3600
Subscribe
Srx380
Subscribe
Srx4000
Subscribe
Srx4100
Subscribe
Srx4200
Subscribe
Srx4600
Subscribe
Srx5000
Subscribe
Srx5400
Subscribe
Srx550
Subscribe
Srx550 Hm
Subscribe
Srx550m
Subscribe
Srx5600
Subscribe
Srx5800
Subscribe
Srx650
Subscribe
|
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2022-27314 | A traffic classification vulnerability in Juniper Networks Junos OS on the SRX Series Services Gateways may allow an attacker to bypass Juniper Deep Packet Inspection (JDPI) rules and access unauthorized networks or resources, when 'no-syn-check' is enabled on the device. While JDPI correctly classifies out-of-state asymmetric TCP flows as the dynamic-application UNKNOWN, this classification is not provided to the policy module properly and hence traffic continues to use the pre-id-default-policy, which is more permissive, causing the firewall to allow traffic to be forwarded that should have been denied. This issue only occurs when 'set security flow tcp-session no-syn-check' is configured on the device. This issue affects Juniper Networks Junos OS on SRX Series: 18.4 versions prior to 18.4R2-S10, 18.4R3-S10; 19.1 versions prior to 19.1R3-S8; 19.2 versions prior to 19.2R1-S8, 19.2R3-S4; 19.3 versions prior to 19.3R3-S3; 19.4 versions prior to 19.4R3-S5; 20.1 versions prior to 20.1R3-S1; 20.2 versions prior to 20.2R3-S2; 20.3 versions prior to 20.3R3-S1; 20.4 versions prior to 20.4R2-S2, 20.4R3; 21.1 versions prior to 21.1R2-S2, 21.1R3; 21.2 versions prior to 21.2R2. This issue does not affect Juniper Networks Junos OS versions prior to 18.4R1. |
Solution
The following software releases have been updated to resolve this specific issue: 18.4R2-S10, 18.4R3-S10, 19.1R3-S8, 19.2R1-S8, 19.2R3-S4, 19.3R3-S3, 19.4R3-S5, 20.1R3-S1, 20.2R3-S2, 20.3R3-S1, 20.4R2-S2, 20.4R3, 21.1R2-S2, 21.1R3, 21.2R2, 21.3R1, and all subsequent releases.
Workaround
Any of the following workarounds will mitigate this issue: 1. Remove 'security flow tcp-session no-syn-check' from the configuration. 2: Enable AppID cache configuration: set services application-identification application-system-cache security-services
| Link | Providers |
|---|---|
| https://kb.juniper.net/JSA11265 |
|
No history.
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: juniper
Published:
Updated: 2024-09-16T23:30:20.864Z
Reserved: 2021-12-21T00:00:00
Link: CVE-2022-22167
No data.
Status : Modified
Published: 2022-01-19T01:15:08.907
Modified: 2024-11-21T06:46:18.000
Link: CVE-2022-22167
No data.
OpenCVE Enrichment
No data.
EUVD