CVE-2022-22153
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 · uneditedAn Insufficient Algorithmic Complexity combined with an Allocation of Resources Without Limits or Throttling vulnerability in the flow processing daemon (flowd) of Juniper Networks Junos OS on SRX Series and MX Series with SPC3 allows an unauthenticated network attacker to cause latency in transit packet processing and even packet loss. If transit traffic includes a significant percentage (> 5%) of fragmented packets which need to be reassembled, high latency or packet drops might be observed. This issue affects Juniper Networks Junos OS on SRX Series, MX Series with SPC3: All versions prior to 18.2R3; 18.3 versions prior to 18.3R3; 18.4 versions prior to 18.4R2-S9, 18.4R3; 19.1 versions prior to 19.1R2; 19.2 versions prior to 19.2R1-S1, 19.2R2.
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 combined Insufficient Algorithmic Complexity and Allocation of Resources Without Limits vulnerability in the flow processing daemon (flowd) of Juniper Networks Junos OS on SRX Series and MX Series with SPC3 allows an unauthenticated network attacker to cause transit packet processing latency and packet loss by sending traffic with a high percentage (>5%) of fragmented packets requiring reassembly.
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.2= 18.2= 18.3= 18.4= 19.1= 19.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 device modelRun 'show chassis hardware' or 'show system information' to confirm the device is an SRX Series or MX Series with SPC3 (Services Processing Card 3)Affected if Device is an SRX Series or MX Series with SPC3
-
Check Junos OS versionRun 'show version' and compare the installed version to the affected range: 18.2, 18.3, 18.4, 19.1, 19.2, or any version before 18.2Affected if Installed version matches any of the affected versions listed (18.2, 18.3, 18.4, 19.1, 19.2) or is earlier than 18.2
-
Verify flowd is activeRun 'show system processes' or check that flow-based forwarding is enabled via 'show security flow status'Affected if Flow processing daemon (flowd) is running and flow-based packet processing is active
-
Confirm transit traffic processingRun 'show security flow session summary' to verify the device is actively processing transit (through) traffic, or check security policies with 'show security policies' to confirm policy permits transit trafficAffected if Device is configured to process transit packets (not solely acting in a chassis cluster or management-only role)
You are affected if your device is an SRX or MX with SPC3, runs a vulnerable Junos version (18.2-19.2 or earlier), and processes transit traffic with flowd enabled.
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 · scoped18.2
Upgrade to a fixed Junos OS version (18.2R3, 18.3R3, 18.4R2-S9/18.4R3, 19.1R2, 19.2R1-S1/19.2R2 or later) per the Juniper advisory; alternatively, implement network-level filtering or rate-limiting of fragmented traffic as a temporary mitigation.
Upgrade to 18.2R3 or later, 18.3R3 or later, 18.4R2-S9/18.4R3 or later, 19.1R2 or later, or 19.2R1-S1/19.2R2 or later (depending on your platform branch)
- 1. Identify the current Junos OS version on the SRX Series or MX Series with SPC3 device using 'show version'
- 2. Confirm the device is an affected version: any version prior to 18.2R3, 18.3 versions prior to 18.3R3, 18.4 versions prior to 18.4R2-S9 or 18.4R3, 19.1 prior to 19.1R2, or 19.2 prior to 19.2R1-S1/19.2R2
- 3. Download the appropriate fixed Junos release from the Juniper Networks support portal based on your hardware platform
- 4. Upload the Junos upgrade package to the device's /var/tmp directory
- 5. Perform the upgrade using 'request system software add /var/tmp/<package-name> reboot'
- 6. After reboot, verify the new version is installed with 'show version'
- 7. Monitor flowd process and network performance to confirm the fragmentation reassembly latency issue is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22153 — 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-22153 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