dbcve.org
JunosOperating system · Juniper

CVE-2023-22412

HIGH · 7.5 CVSS v3.1 Published 2023-01-13
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 with MS-MPC or MS-MIC card and SRX Series allows an unauthenticated, network-based attacker to cause a flow processing 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 occurs when SIP ALG is enabled and specific SIP messages are processed simultaneously. This issue affects: Juniper Networks Junos OS on MX Series and SRX Series 20.4 versions prior to 20.4R3-S4; 21.1 versions prior to 21.1R3-S3; 21.2 versions prior to 21.2R3-S2; 21.3 versions prior to 21.3R3; 21.4 versions prior to 21.4R3; 22.1 versions prior to 22.1R2. This issue does not affect Juniper Networks Junos OS versions prior to 20.4R1 on MX Series, or SRX Series.

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 (Session Initiation Protocol Application Layer Gateway) of Juniper Networks Junos OS on MX Series (with MS-MPC or MS-MIC cards) and SRX Series allows an unauthenticated, network-based attacker to cause the flow processing daemon (flowd) to crash by sending specific SIP messages simultaneously, resulting in sustained DoS conditions.

MitigationUpgrade Junos OS to a patched version (20.4R3-S4, 21.1R3-S3, 21.2R3-S2, 21.3R3, 21.4R3, or 22.1R2 or later) or disable SIP ALG if upgrade 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.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 the device model
    Run 'show chassis hardware' or check the device model to confirm it is an MX Series router or SRX Series firewall
    Affected if The device is not an MX Series (with MS-MPC or MS-MIC cards) or SRX Series, then it is not affected by this specific CVE
  2. Check the Junos OS version
    Run 'show version' to obtain the installed Junos OS version
    Affected if The installed version is 20.4, 21.1, 21.2, 21.3, 21.4, or 22.1, then it matches the affected versions listed in the CVE
  3. Verify SIP ALG is enabled
    Run 'show security alg sip' to check the SIP ALG status
    Affected if SIP ALG is enabled, then the vulnerability is present and exploitable; if SIP ALG is disabled, the device is not affected by this flaw
  4. Confirm MS-MPC or MS-MIC presence (MX Series only)
    For MX Series devices, run 'show chassis fpc' or 'show chassis hardware' to verify the presence of MS-MPC or MS-MIC cards
    Affected if The device is MX Series without MS-MPC or MS-MIC cards, the SIP ALG vulnerability in this CVE does not apply; these cards are required for the affected SIP ALG implementation

The device is affected if it is an MX Series with MS-MPC/MS-MIC cards or an SRX Series, running Junos OS version 20.4, 21.1, 21.2, 21.3, 21.4, or 22.1, with SIP ALG enabled.

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 Junos OS to a patched version (20.4R3-S4, 21.1R3-S3, 21.2R3-S2, 21.3R3, 21.4R3, or 22.1R2 or later) or disable SIP ALG if upgrade is not immediately feasible.

Recommended fix High confidence

20.4R3-S4 (or later: 21.1R3-S3, 21.2R3-S2, 21.3R3, 21.4R3, or 22.1R2)

  1. 1. Identify the current Junos OS version on the affected MX Series (with MS-MPC/MS-MIC) or SRX Series devices using 'show version'
  2. 2. Confirm SIP ALG is enabled by running 'show security alg sip'
  3. 3. Schedule a maintenance window for the upgrade as it requires a system reboot
  4. 4. Download the appropriate fixed Junos OS version from the Juniper Networks support portal: 20.4R3-S4, 21.1R3-S3, 21.2R3-S2, 21.3R3, 21.4R3, or 22.1R2
  5. 5. Upload the Junos OS upgrade package to the device using 'file copy' or FTP/SCP
  6. 6. Initiate the upgrade with 'request system software add <package-name> reboot'
  7. 7. After reboot, verify the new version with 'show version' and confirm SIP ALG status with 'show security alg sip'
  8. 8. Test SIP call functionality to confirm the SIP ALG is functioning properly
Caveat Standard Junos OS upgrade risks apply - ensure compatibility with other network devices and review release notes for any behavior changes

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

Fix this in Junos Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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