Skip to content
CVE Tracker
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2022-22167

Junos OS: SRX Series: If no-syn-check is enabled, traffic classified as UNKNOWN gets permitted by pre-id-default-policy

High7.2EPSS 0.67%
Published
Updated
Reserved
Assigned by
juniper

Description

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.

Scores

CVSS scores of CVE-2022-22167, by who scored it
Scored byCVSSScoreVector
juniperCNA (assigner)3.1High7.2CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
NVDNVD · Modified3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.67% · top 48% of all CVEs (7 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.2.

Weakness

Affected products

  • Juniper Networks · Junos OS

    • affected 18.4 – < 18.4R2-S10, 18.4R3-S10
    • affected 19.1 – < 19.1R3-S8
    • affected 19.2 – < 19.2R1-S8, 19.2R3-S4
    • affected 19.3 – < 19.3R3-S3
    • affected 19.4 – < 19.4R3-S5
    • affected 20.1 – < 20.1R3-S1
    • affected 20.2 – < 20.2R3-S2
    • affected 20.3 – < 20.3R3-S1
    • affected 20.4 – < 20.4R2-S2, 20.4R3
    • affected 21.1 – < 21.1R2-S2, 21.1R3
    • affected 21.2 – < 21.2R2

  • Juniper Networks · Junos OS

    • unaffected unspecified – < 18.4R1

What to do

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

Exploitation: Juniper SIRT is not aware of any malicious exploitation of this vulnerability.

References (1)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2022-22167 badge
[![CVE-2022-22167](https://trackcve.app/badge/CVE-2022-22167.svg)](https://trackcve.app/cve/CVE-2022-22167)

Record last updated .