CVE-2022-22157Network attack vector

Firewall policy bypass via permissive flow misclassification

Published Jan 19, 2022 · Updated Sep 17, 2024

Traffic classification in Juniper Networks Junos OS on SRX Series allows remote attackers to bypass JDPI rules via asymmetric TCP flows. JDPI labels out-of-state asymmetric TCP flows INCONCLUSIVE instead of UNKNOWN, applying the more permissive disposition. The device must have no-syn-check configured; matching traffic can then reach networks or resources that firewall policy should deny.

CVSS severity7.2
High
EPSS probability0.66%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Traffic classification in Juniper Networks Junos OS on SRX Series allows remote attackers to bypass JDPI rules via asymmetric TCP flows. JDPI labels out-of-state asymmetric TCP flows INCONCLUSIVE instead of UNKNOWN, applying the more permissive disposition. The device must have no-syn-check configured; matching traffic can then reach networks or resources that firewall policy should deny.

The record

CVE
CVE-2022-22157
Published
Jan 19, 2022
Updated
Sep 17, 2024
Vendor
Juniper Networks
Product
Junos OS
Classifications
CWE-863
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Jan 19, 2022CVE publishedPublication date reported by the CVE source.
  2. 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.

  1. Affected versionversion=18.4 <18.4R2-S9, 18.4R3-S9
  2. Affected versionversion=19.1 <19.1R2-S3, 19.1R3-S6
  3. Affected versionversion=19.2 <19.2R1-S7, 19.2R3-S3
  4. Affected versionversion=19.3 <19.3R2-S6, 19.3R3-S2
  5. Affected versionversion=19.4 <19.4R2-S5, 19.4R3-S3
  6. Affected versionversion=20.1 <20.1R2-S2, 20.1R3
  7. Affected versionversion=20.2 <20.2R3-S1
  8. Affected versionversion=20.3 <20.3R3
  9. Affected versionversion=20.4 <20.4R2-S1, 20.4R3
  10. Affected versionversion=21.1 <21.1R1-S1, 21.1R2

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Juniper Networks · Junos OSversion=18.4 <18.4R2-S9, 18.4R3-S9; version=19.1 <19.1R2-S3, 19.1R3-S6; version=19.2 <19.2R1-S7, 19.2R3-S3; version=19.3 <19.3R2-S6, 19.3R3-S2; version=19.4 <19.4R2-S5, 19.4R3-S3; version=20.1 <20.1R2-S2, 20.1R3; version=20.2 <20.2R3-S1; version=20.3 <20.3R3; version=20.4 <20.4R2-S1, 20.4R3; version=21.1 <21.1R1-S1, 21.1R2

Published CVSS scores

7.2Juniper NetworksCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
9.3NIST NVDCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N
5.8NIST NVDAV:N/AC:M/Au:N/C:P/I:P/A:N

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.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-863Incorrect Authorization

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