dbcve.org
JunosOperating system · Juniper

CVE-2022-22198

HIGH · 7.5 CVSS v3.1 Published 2022-04-14
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 Access of Uninitialized Pointer vulnerability in the SIP ALG of Juniper Networks Junos OS allows an unauthenticated network-based attacker to cause a Denial of Service (DoS). Continued receipt of these specific packets will cause a sustained Denial of Service condition. On all MX and SRX platforms, if the SIP ALG is enabled, an MS-MPC or MS-MIC, or SPC will crash if it receives a SIP message with a specific contact header format. This issue affects Juniper Networks Junos OS on MX Series and SRX Series: 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 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 uninitialized pointer in the SIP Application Layer Gateway (ALG) of Juniper Junos OS allows an unauthenticated remote attacker to crash the MS-MPC/MS-MIC/SPC cards by sending specially crafted SIP messages with a specific Contact header format. The vulnerability is only exploitable when SIP ALG is enabled on MX or SRX platforms.

MitigationDisable SIP ALG if not required, or upgrade Junos OS to version 20.4R3, 21.1R2-S1/21.1R3, or 21.2R2 or later. If SIP ALG is required and cannot be upgraded immediately, implement network-level filtering to block malformed SIP messages.

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

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 platform type
    Run 'show system hardware' or check the device model to confirm it is an MX Series or SRX Series device
    Affected if Device is NOT an MX or SRX platform - those are the only affected platforms
  2. Check Junos OS version
    Run 'show version' and compare the installed version against the affected versions: 20.4, 21.1, 21.2
    Affected if Version is 20.4, 21.1, or 21.2 exactly - only these specific versions are vulnerable
  3. Verify SIP ALG is enabled
    Run 'show security alg sip' or check 'show configuration security alg sip' to see if SIP ALG is configured and active
    Affected if SIP ALG is enabled - the vulnerability is only exploitable when SIP ALG is turned on
  4. Check for MS-MPC/MS-MIC/SPC cards
    Run 'show chassis hardware' or 'show chassis fpc' to list installed line cards
    Affected if MS-MPC, MS-MIC, or SPC cards are present - these are the specific card types that can be crashed by the exploit

User is affected if: device is MX or SRX platform AND Junos version is exactly 20.4, 21.1, or 21.2 AND SIP ALG is enabled AND MS-MPC/MS-MIC/SPC cards are installed

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 SIP ALG if not required, or upgrade Junos OS to version 20.4R3, 21.1R2-S1/21.1R3, or 21.2R2 or later. If SIP ALG is required and cannot be upgraded immediately, implement network-level filtering to block malformed SIP messages.

Recommended fix High confidence

20.4R3, 21.1R3 (or 21.1R2-S1), or 21.2R2 depending on current branch

  1. 1. Identify the current Junos OS version by running 'show version' on the device
  2. 2. Verify if SIP ALG is enabled by running 'show security alg sip' or checking the configuration under 'set security alg sip'
  3. 3. Determine the appropriate upgrade path based on current version: for 20.4 branch upgrade to 20.4R3 or later; for 21.1 branch upgrade to 21.1R2-S1 or 21.1R3 or later; for 21.2 branch upgrade to 21.2R2 or later
  4. 4. Schedule a maintenance window for the upgrade
  5. 5. Download the appropriate Junos OS upgrade image from the Juniper Networks support portal
  6. 6. Upload the upgrade image to the device and initiate the upgrade using 'request system software add <package> reboot'
  7. 7. After reboot, verify the new version with 'show version'
  8. 8. Confirm SIP ALG functionality is operational

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

Fix this in Junos Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-22198 — 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-22198 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