dbcve.org
JunosOperating system · Juniper

CVE-2022-22175

HIGH · 7.5 CVSS v3.1 Published 2022-01-19
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 Locking vulnerability in the SIP ALG of Juniper Networks Junos OS on MX Series and SRX Series allows an unauthenticated networked attacker to cause a flowprocessing daemon (flowd) crash and thereby a Denial of Service (DoS). Continued receipt of these specific packets will cause a sustained Denial of Service condition. This issue can occur in a scenario where the SIP ALG is enabled and specific SIP messages are being processed simultaneously. This issue affects: Juniper Networks Junos OS on MX Series and SRX Series 20.4 versions prior to 20.4R3-S1; 21.1 versions prior to 21.1R2-S2, 21.1R3; 21.2 versions prior to 21.2R1-S2, 21.2R2; 21.3 versions prior to 21.3R1-S1, 21.3R2. This issue does not affect Juniper Networks Junos OS versions prior to 20.4R1.

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

An improper locking vulnerability in the SIP ALG (Application Layer Gateway) on Juniper Networks Junos OS for MX Series and SRX Series allows an unauthenticated remote attacker to crash the flowd (flow processing daemon) by sending specific SIP messages while the SIP ALG is enabled and processing simultaneous SIP messages, resulting in sustained DoS.

MitigationDisable the SIP ALG if not required, or upgrade Junos OS to the patched version (20.4R3-S1, 21.1R2-S2/21.1R3, 21.2R1-S2/21.2R2, or 21.3R1-S1/21.3R2 depending on the release train).

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.4= 21.1= 21.2= 21.3

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 model
    Run 'show chassis hardware' or 'show system information' to confirm the device is an MX Series or SRX Series router
    Affected if Device is not MX Series or SRX Series (vulnerability only affects these platforms)
  2. Check Junos OS version
    Run 'show version' to obtain the installed Junos OS version
    Affected if Version matches 20.4, 21.1, 21.2, or 21.3 release trains (e.g., 20.4R1, 21.1R1, etc.)
  3. Verify SIP ALG is enabled
    Run 'show security alg sip' to check if the SIP ALG is active, or inspect configuration with 'show security alg' and look for 'sip' under the ALG settings
    Affected if SIP ALG is enabled (vulnerability only triggers when SIP ALG processes SIP traffic)
  4. Check flowd daemon status
    Run 'show system processes extensive | match flowd' to check if the flowd process is running, or look for recent core dumps with 'show system core-dumps'
    Affected if Flowd process is absent, crashed, or core dumps exist (indicates the vulnerability may have been triggered)

Device is affected if it is an MX/SRX Series running Junos 20.4/21.1/21.2/21.3 with SIP ALG enabled and flowd has crashed or is unstable.

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

Disable the SIP ALG if not required, or upgrade Junos OS to the patched version (20.4R3-S1, 21.1R2-S2/21.1R3, 21.2R1-S2/21.2R2, or 21.3R1-S1/21.3R2 depending on the release train).

Recommended fix High confidence

20.4R3-S1, 21.1R2-S2/21.1R3, 21.2R1-S2/21.2R2, or 21.3R1-S1/21.3R2 (depending on starting branch)

  1. 1. Identify the current Junos OS version on the affected MX Series or SRX Series device using 'show version'
  2. 2. Verify SIP ALG is enabled by checking the configuration with 'show configuration security alg sip'
  3. 3. If SIP ALG is enabled and the device is on an affected version (20.4, 21.1, 21.2, or 21.3), plan for upgrade to a fixed release
  4. 4. For 20.4 branch: upgrade to 20.4R3-S1 or later
  5. 5. For 21.1 branch: upgrade to 21.1R2-S2 or 21.1R3 or later
  6. 6. For 21.2 branch: upgrade to 21.2R1-S2 or 21.2R2 or later
  7. 7. For 21.3 branch: upgrade to 21.3R1-S1 or 21.3R2 or later
  8. 8. Download the appropriate upgrade package from the Juniper Networks support portal
Caveat Standard Junos OS upgrade considerations apply - review release notes for any behavioral changes and plan maintenance window

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-22175 — 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-22175 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