CVE-2022-22185
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 · uneditedA vulnerability in Juniper Networks Junos OS on SRX Series, allows a network-based unauthenticated attacker to cause a Denial of Service (DoS) by sending a specific fragmented packet to the device, resulting in a flowd process crash, which is responsible for packet forwarding. Continued receipt and processing of this specific packet will create a sustained DoS condition. This issue only affects SRX Series when 'preserve-incoming-fragment-size' feature is enabled. This issue affects Juniper Networks Junos OS on SRX Series: 18.3 versions prior to 18.3R3-S6; 18.4 versions prior to 18.4R3-S10; 19.1 versions prior to 19.1R3-S7; 19.2 versions prior to 19.2R3-S4; 19.3 versions prior to 19.3R3-S4; 19.4 versions prior to 19.4R3-S6; 20.1 versions prior to 20.1R3-S2; 20.2 versions prior to 20.2R3-S3; 20.3 versions prior to 20.3R3-S1; 20.4 versions prior to 20.4R3; 21.1 versions prior to 21.1R2-S1, 21.1R3; 21.2 versions prior to 21.2R2. This issue does not affect Juniper Networks Junos OS prior to 17.3R1.
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 confidenceA denial-of-service vulnerability exists in Juniper Networks Junos OS on SRX Series devices where a network-based unauthenticated attacker can send a specific fragmented packet to crash the flowd process, which handles packet forwarding. This only affects devices with the 'preserve-incoming-fragment-size' feature enabled, and continued receipt of the malicious packets creates a sustained DoS condition.
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= 18.3= 18.4= 19.1= 19.2= 19.3= 19.4= 20.1= 20.2= 20.3= 20.4= 21.1= 21.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Junos OS versionRun 'show version' on the device CLI and note the version number in the output (for example, the line showing 'Junos: 20.4 ...')Affected if The version matches 18.3, 18.4, 19.1, 19.2, 19.3, 19.4, 20.1, 20.2, 20.3, 20.4, 21.1, or 21.2
-
Confirm device is SRX SeriesRun 'show chassis hardware' or look for the model number in 'show version' output (typically shows 'SRX' in the model name)Affected if The hardware model is an SRX Series security appliance
-
Check if preserve-incoming-fragment-size is enabledRun 'show configuration security flow' or 'show configuration | match preserve-incoming-fragment-size' to inspect the security flow settingsAffected if The 'preserve-incoming-fragment-size' option appears in the active configuration under the security flow hierarchy
The device is affected if it runs a listed Junos version, is an SRX Series model, AND has the preserve-incoming-fragment-size feature configured and active.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade Junos OS to the fixed versions specified (18.3R3-S6 and later, 18.4R3-S10 and later, etc.) or consider disabling the 'preserve-incoming-fragment-size' feature if upgrade is not immediately feasible.
Upgrade to the first fixed release in your current branch: 18.3R3-S6, 18.4R3-S10, 19.1R3-S7, 19.2R3-S4, 19.3R3-S4, 19.4R3-S6, 20.1R3-S2, 20.2R3-S3, 20.3R3-S1, 20.4R3, 21.1R3, or 21.2R2 depending on your starting version. For the latest security position, consider upgrading to the most recent stable
- 1. Identify the current Junos OS version running on the SRX Series device using 'show version' command
- 2. Identify if the 'preserve-incoming-fragment-size' feature is enabled using 'show security flow' command and checking for the configuration under 'set security flow'
- 3. If the device is running an affected version (18.3 versions prior to 18.3R3-S6, 18.4 prior to 18.4R3-S10, 19.1 prior to 19.1R3-S7, 19.2 prior to 19.2R3-S4, or later affected versions as listed), plan for upgrade
- 4. Download the appropriate fixed Junos OS release for your version branch from the Juniper Networks download portal
- 5. Upload the Junos OS upgrade package to the SRX device via SCP or USB
- 6. Perform the upgrade using 'request system software add <package-name>' command
- 7. Reboot the device after upgrade completes using 'request system reboot'
- 8. After reboot, verify the new version is installed using 'show version' and confirm the flowd process is running using 'show system processes'
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22185 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-22185 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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