JunosOperating system · Juniper

CVE-2022-22233

MEDIUM · 5.5 CVSS v3.1 Published 2022-10-18

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

57/100

Remediation priority · Elevated

Zero-click

Official description

NVD · unedited

An Unchecked Return Value to NULL Pointer Dereference vulnerability in Routing Protocol Daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows a locally authenticated attacker with low privileges to cause a Denial of Service (DoS). In Segment Routing (SR) to Label Distribution Protocol (LDP) interworking scenario, configured with Segment Routing Mapping Server (SRMS) at any node, when an Area Border Router (ABR) leaks the SRMS entries having "S" flag set from IS-IS Level 2 to Level 1, an rpd core might be observed when a specific low privileged CLI command is issued. This issue affects: Juniper Networks Junos OS 21.4 versions prior to 21.4R1-S2, 21.4R2-S1, 21.4R3; 22.1 versions prior to 22.1R2. Juniper Networks Junos OS Evolved 21.4-EVO versions prior to 21.4R1-S2-EVO, 21.4R2-S1-EVO, 21.4R3-EVO; 22.1-EVO versions prior to 22.1R2-EVO. This issue does not affect: Juniper Networks Junos OS versions prior to 21.4R1. Juniper Networks Junos OS Evolved versions prior to 21.4R1-EVO.

Technical summary

dbcve analysis · high confidence

A NULL pointer dereference in the Routing Protocol Daemon (rpd) occurs when processing Segment Routing Mapping Server (SRMS) entries with the 'S' flag during IS-IS Level 2 to Level 1 leaking on an Area Border Router in SR-to-LDP interworking scenarios. When a low-privileged user issues a specific CLI command in this configuration, an unchecked return value causes rpd to crash, resulting in denial of service.

MitigationUpgrade Junos OS to 21.4R1-S2, 21.4R2-S1, 21.4R3, 22.1R2 or later (or corresponding Junos OS Evolved versions). This is a local DoS requiring authenticated low-privilege access, but the specific SR-to-LDP interworking configuration must be present.

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:= 21.4= 22.1

Junos Os EvolvedOperating system

Affected:= 21.4= 22.1

CVSS breakdown

From the vector

Attack vector: Local
Complexity: Low
Privileges: Low
User interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

CVSS:3.1/AV:L/AC:L/PR:L/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.

Check Junos version

Run 'show version' or 'show version detail' to identify the installed Junos or Junos OS Evolved version

Affected if Version is 21.4 or 22.1 (any build within these releases)
Verify IS-IS protocol is enabled

Run 'show isis interface' to confirm IS-IS is active on any interfaces

Affected if IS-IS protocol is configured and running on the device
Confirm Area Border Router configuration

Run 'show isis adjacency' and check for both Level 1 and Level 2 neighbors, or examine configuration for 'level 1' and 'level 2' under the IS-IS hierarchy

Affected if Device acts as an ABR with both IS-IS Level 1 and Level 2 adjacencies or protocols enabled
Check for IS-IS Level 2 to Level 1 leaking

Run 'show configuration protocols isis | display set' or inspect the IS-IS configuration for 'level 2 leak' or 'export' policies that leak routes from Level 2 to Level 1

Affected if IS-IS configuration includes Level 2 to Level 1 route leaking
Verify SR-to-LDP interworking configuration

Run 'show configuration | match sr-to-ldp' or examine the configuration for Segment Routing to LDP interworking settings under the protocols hierarchy

Affected if SR-to-LDP interworking is configured on the device
Check for SRMS entries with 'S' flag

Run 'show configuration segment-routing mapping-server' and look for mapping entries that include the 'S' flag, or check the active SRMS policy configuration

Affected if Segment Routing Mapping Server entries with the 'S' flag are configured

Device is affected if it runs Junos 21.4 or 22.1, operates as an IS-IS ABR with Level 2 to Level 1 leaking, has SR-to-LDP interworking configured, and uses SRMS entries with the 'S' flag in this specific configuration.

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 to 21.4R1-S2, 21.4R2-S1, 21.4R3, 22.1R2 or later (or corresponding Junos OS Evolved versions). This is a local DoS requiring authenticated low-privilege access, but the specific SR-to-LDP interworking configuration must be present.

Recommended fix High confidence

Junos OS: upgrade to 21.4R1-S2, 21.4R2-S1, 21.4R3, 22.1R2 or later; Junos OS Evolved: upgrade to 21.4R1-S2-EVO, 21.4R2-S1-EVO, 21.4R3-EVO, 22.1R2-EVO or later

1. Identify current Junos OS or Junos OS Evolved version using 'show version' command
2. Confirm the device is in an SR to LDP interworking scenario with SRMS configured
3. Schedule a maintenance window for the upgrade
4. Download the appropriate fixed release for your platform: 21.4R1-S2, 21.4R2-S1, 21.4R3 or later for Junos OS; 21.4R1-S2-EVO, 21.4R2-S1-EVO, 21.4R3-EVO or later for Junos OS Evolved
5. For Junos OS: upload the junos-arm-32-bit or junos-arm-64-bit or appropriate platform package to /var/tmp
6. For Junos OS Evolved: upload the iso image to /var/tmp
7. Execute 'request system software add <package>' with the appropriate options for your platform
8. Reboot the device using 'request system reboot'

Caveat Standard Junos upgrade risks apply - ensure proper backups and have console access available in case of issues

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

Fix this in Junos Scoped from the published advisory

Consultation2.0 h
Implementation1.0 h
Testing2.0 h
Review / QA1.0 h

6.0 hours of engineering $1,060

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2022-22233 — 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-22233 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2022-22233?

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 5.5 Medium

Exploit likelihood EPSS, next 30 days 0.2%

Affects: Junos

Remediation

Need this fixed?

Fix this in Junos 6 hrs · Moderate

Typical engagement from $1,060

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2022-22233 and return a fixed quote.

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