dbcve.org
JunosOperating system · Juniper

CVE-2022-22235

HIGH · 7.5 CVSS v3.1 Published 2022-10-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An Improper Check for Unusual or Exceptional Conditions vulnerability in the Packet Forwarding Engine (PFE) of Juniper Networks Junos OS on SRX Series allows an unauthenticated, network-based, attacker to cause Denial of Service (DoS). A PFE crash will happen when a GPRS Tunnel Protocol (GTP) packet is received with a malformed field in the IP header of GTP encapsulated General Packet Radio Services (GPRS) traffic. The packet needs to match existing state which is outside the attackers control, so the issue cannot be directly exploited. The issue will only be observed when endpoint address validation is enabled. This issue affects Juniper Networks Junos OS on SRX Series: 20.2 versions prior to 20.2R3-S5; 20.3 versions prior to 20.3R3-S4; 20.4 versions prior to 20.4R3-S3; 21.1 versions prior to 21.1R3-S2; 21.2 versions prior to 21.2R3-S1; 21.3 versions prior to 21.3R3; 21.4 versions prior to 21.4R1-S2, 21.4R2; 22.1 versions prior to 22.1R1-S1, 22.1R2. This issue does not affect Juniper Networks Junos OS versions prior to 20.2R1.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A vulnerability in Juniper Networks Junos OS on SRX Series allows an unauthenticated network attacker to cause a Packet Forwarding Engine (PFE) crash via malformed GPRS Tunnel Protocol (GTP) packets. The attack requires GTP traffic matching an existing state and endpoint address validation to be enabled, making direct exploitation difficult but still achievable under specific conditions.

MitigationUpgrade to Junos OS versions 20.2R3-S5, 20.3R3-S4, 20.4R3-S3, 21.1R3-S2, 21.2R3-S1, 21.3R3, 21.4R1-S2, 21.4R2, or 22.1R1-S1/22.1R2 as appropriate. Alternatively, disable endpoint address validation in the GTP profile if upgrading is not immediately feasible.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
JunosOperating system
Affected:= 20.2= 20.3= 20.4= 21.1= 21.2= 21.3= 21.4= 22.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify device platform
    Run 'show chassis hardware' or check device model to confirm it is an SRX Series device
    Affected if Device is not an SRX Series device - this CVE only affects SRX Series
  2. Check Junos OS version
    Run 'show version' to obtain the installed Junos OS version
    Affected if Version matches 20.2, 20.3, 20.4, 21.1, 21.2, 21.3, 21.4, or 22.1 (any variant within these releases)
  3. Verify GTP is configured
    Run 'show configuration | match gtp' or check the security policy configuration for GTP-u or GTP-c tunnel services
    Affected if GTP tunneling is not configured - the vulnerability requires GTP traffic matching an existing state to be present
  4. Check endpoint address validation setting
    Run 'show configuration services gtp' and look for 'endpoint-address-validation' under the GTP profile, or check the specific GTP profile applied to your GTP policy
    Affected if Endpoint address validation is enabled - the CVE requires this feature to be enabled for exploitation

A user is affected if they are running an affected Junos version on SRX Series with GTP configured and endpoint address validation enabled in the GTP profile.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Junos OS versions 20.2R3-S5, 20.3R3-S4, 20.4R3-S3, 21.1R3-S2, 21.2R3-S1, 21.3R3, 21.4R1-S2, 21.4R2, or 22.1R1-S1/22.1R2 as appropriate. Alternatively, disable endpoint address validation in the GTP profile if upgrading is not immediately feasible.

Recommended fix High confidence

Upgrade to 20.2R3-S5 / 20.3R3-S4 / 20.4R3-S3 / 21.1R3-S2 / 21.2R3-S1 / 21.3R3 / 21.4R2 / 22.1R2 or later based on current version

  1. 1. Identify the current Junos OS version on the SRX Series device using 'show version' command.
  2. 2. Based on the current version, upgrade to the fixed release: For 20.2.x upgrade to 20.2R3-S5 or later; For 20.3.x upgrade to 20.3R3-S4 or later; For 20.4.x upgrade to 20.4R3-S3 or later; For 21.1.x upgrade to 21.1R3-S2 or later; For 21.2.x upgrade to 21.2R3-S1 or later; For 21.3.x upgrade to 21.3R3 or later; For 21.4.x upgrade to 21.4R2 or later; For 22.1.x upgrade to 22.1R2 or later.
  3. 3. Upload the Junos upgrade package to the device via FTP/SCP.
  4. 4. Execute 'request system software add <package-name>' to install the upgrade.
  5. 5. Reboot the device using 'request system reboot' to apply changes.
  6. 6. After reboot, verify the new version is installed with 'show version' and confirm the GTP endpoint address validation feature functions correctly.
Caveat Standard Junos upgrade risks apply - verify compatibility with other network devices and review release notes for any configuration changes before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Junos Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-22235 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-22235 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data