JunosOperating system · Juniper

CVE-2022-22184

HIGH · 7.5 CVSS v3.1 Published 2022-12-22

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

NVD · unedited

An Improper Input Validation vulnerability in the Routing Protocol Daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows an unauthenticated network-based attacker to cause a Denial of Service (DoS). If a BGP update message is received over an established BGP session, and that message contains a specific, optional transitive attribute, this session will be torn down with an update message error. This issue cannot propagate beyond an affected system as the processing error occurs as soon as the update is received. This issue is exploitable remotely as the respective attribute will propagate through unaffected systems and intermediate AS (if any). Continuous receipt of a BGP update containing this attribute will create a sustained Denial of Service (DoS) condition. Since this issue only affects 22.3R1, Juniper strongly encourages customers to move to 22.3R1-S1. Juniper SIRT felt that the need to promptly warn customers about this issue affecting the 22.3R1 versions of Junos OS and Junos OS Evolved warranted an Out of Cycle JSA. This issue affects: Juniper Networks Junos OS version 22.3R1. Juniper Networks Junos OS Evolved version 22.3R1-EVO. This issue does not affect: Juniper Networks Junos OS versions prior to 22.3R1. Juniper Networks Junos OS Evolved versions prior to 22.3R1-EVO.

Technical summary

dbcve analysis · high confidence

A vulnerability in Junos OS and Junos OS Evolved 22.3R1 allows an unauthenticated attacker to cause denial of service by sending a specially crafted BGP update message containing a specific optional transitive attribute. The malformed update triggers an error in the Routing Protocol Daemon (rpd), causing the BGP session to be torn down, and continuous receipt creates a sustained DoS condition.

MitigationUpgrade Junos OS or Junos OS Evolved to version 22.3R1-S1 or later. Until upgrade is possible, monitor for BGP session flapping and consider filtering suspicious BGP attributes at border routers.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

JunosOperating system

Affected:= 22.3

Junos Os EvolvedOperating system

Affected:= 22.3

CVSS breakdown

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?

dbcve checks

Work through these to decide whether this CVE applies to you.

Verify Junos OS version

Run 'show version' or 'show version detail' to display the installed Junos OS version. Check if the version string matches 22.3 without any S1 or later suffix (e.g., 22.3R1, 22.3R1-S1, 22.3R2, etc.)

Affected if The installed version is 22.3R1 without any S1 or later patch (e.g., 22.3R1-S1, 22.3R2, etc.)
Confirm Junos OS Evolved version

Run 'show version' on Junos OS Evolved to display the installed version. Verify if it is version 22.3 without any S1 or later update

Affected if The installed Junos OS Evolved version is 22.3 without the S1 patch or later
Check if BGP is enabled

Run 'show bgp summary' or 'show protocols bgp' to determine if BGP is configured and active on the device

Affected if BGP is configured and running on the device
Monitor for BGP session drops

Review logs using 'show log messages' or 'show bgp neighbor' output for repeated BGP session teardowns, error messages related to rpd, or BGP update errors occurring around the same time

Affected if BGP sessions are frequently dropping or rpd errors are present in system logs
Inspect rpd daemon status

Run 'show system processes routing' or check rpd process status to verify the Routing Protocol Daemon is stable and not crashing repeatedly

Affected if The rpd process is unstable, crashing, or showing restart cycles

A device is affected if it runs Junos OS or Junos OS Evolved version 22.3 without the S1 patch or later, and has BGP enabled and processing incoming BGP updates.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Upgrade Junos OS or Junos OS Evolved to version 22.3R1-S1 or later. Until upgrade is possible, monitor for BGP session flapping and consider filtering suspicious BGP attributes at border routers.

Recommended fix High confidence

22.3R1-S1 or later

Plan a maintenance window for the upgrade
Download the Junos OS 22.3R1-S1 (or later) software image from the Juniper Networks support portal
Upload the new software image to the device using FTP/SCP or USB
Verify the software image integrity using the 'request system software validate' command
Initiate the software installation using 'request system software add <image-name> reboot' command
After the device reboots, verify the new version with 'show version'
Verify BGP peers are up and operating normally using 'show bgp summary'

Caveat Review Junos OS 22.3R1-S1 release notes for any potential breaking changes before upgrading

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
Testing6.0 h
Review / QA3.0 h

21.0 hours of engineering $3,680

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

kb.juniper.netVendor Advisory
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-22184 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2022-22184?

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.

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

At a glance

A fix existsA vendor remedy is published

Severity 7.5 High

Exploit likelihood EPSS, next 30 days 0.7%

Affects: Junos

Remediation

A high-priority fix

Fix this in Junos 21 hrs · Moderate

Typical engagement from $3,680

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2022-22184 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References