JunosOperating system · Juniper

CVE-2023-44175

HIGH · 7.5 CVSS v3.1 Published 2023-10-12

Fix available

A fix is available. Upgrade to 20.4 or later.

See remediation →

84/100

Remediation priority · High

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

A Reachable Assertion vulnerability in the routing protocol daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows to send specific genuine PIM packets to the device resulting in rpd to crash causing a Denial of Service (DoS). Continued receipt and processing of this packet will create a sustained Denial of Service (DoS) condition. Note: This issue is not noticed when all the devices in the network are Juniper devices. This issue affects Juniper Networks: Junos OS: * All versions prior to 20.4R3-S7; * 21.2 versions prior to 21.2R3-S5; * 21.3 versions prior to 21.3R3-S4; * 21.4 versions prior to 21.4R3-S4; * 22.1 versions prior to 22.1R3-S4; * 22.2 versions prior to 22.2R3; * 22.3 versions prior to 22.3R3; * 22.4 versions prior to 22.4R3. Junos OS Evolved: * All versions prior to 22.3R3-EVO; * 22.4-EVO versions prior to 22.4R3-EVO; * 23.2-EVO versions prior to 23.2R1-EVO.

Technical summary

dbcve analysis · high confidence

A reachable assertion vulnerability in the routing protocol daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows remote attackers to cause a denial of service by sending specific genuine PIM (Protocol Independent Multicast) packets that trigger an assertion failure in rpd, causing the daemon to crash.

MitigationApply the vendor-supplied software updates for Junos OS or Junos OS Evolved to the fixed versions specified in the advisory. Until patching is possible, consider filtering or rate-limiting untrusted PIM traffic at network boundaries.

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:< 20.4= 20.4= 21.2= 21.3= 21.4= 22.1= 22.2= 22.3= 22.4

Junos Os EvolvedOperating system

Affected:= 22.3= 22.4= 23.2

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 PIM protocol is enabled on the device

Run 'show protocols pim' or check the configuration under 'protocols pim' hierarchy using 'show configuration protocols pim'

Affected if PIM is enabled and configured - the vulnerability is only triggerable when PIM is active
Confirm the Junos OS or Junos OS Evolved version

Run 'show version' or 'show version detail' to obtain the exact software version

Affected if The installed version matches one of the affected versions: Junos < 20.4, = 20.4, = 21.2, = 21.3, = 21.4, = 22.1, = 22.2, = 22.3, = 22.4; or Junos OS Evolved = 22.3, = 22.4, = 23.2
Check rpd daemon status

Run 'show system processes routing' or 'systemctl status rpd' on Evolved variants to verify the routing daemon is running

Affected if rpd is running - this is the daemon that will crash when the vulnerability is triggered
Inspect logs for rpd crashes or assertion failures

Run 'show log messages' and search for 'rpd' crash, assertion, or PIM-related errors using 'show log messages | match rpd'

Affected if Recent rpd crashes or assertion failures related to PIM are logged, indicating possible exploitation attempts

You are affected if PIM protocol is enabled on a Junos device running any of the specified affected versions, and the device is exposed to PIM traffic that could trigger the rpd assertion failure.

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

Remediation

dbcve · scoped

Upgrade available Upgrade to 20.4 or later

Fixed in 20.4

Interim mitigation

Apply the vendor-supplied software updates for Junos OS or Junos OS Evolved to the fixed versions specified in the advisory. Until patching is possible, consider filtering or rate-limiting untrusted PIM traffic at network boundaries.

Recommended fix High confidence

Junos OS: 20.4R3-S7, 21.2R3-S5, 21.3R3-S4, 21.4R3-S4, 22.1R3-S4, 22.2R3, 22.3R3, or 22.4R3 (or later); Junos OS Evolved: 22.3R3-EVO, 22.4R3-EVO, or 23.2R1-EVO (or later)

1. Identify the current Junos OS or Junos OS Evolved version running on the device using 'show version'
2. Determine the appropriate upgrade path based on current version: for Junos OS upgrade to 20.4R3-S7 or later, 21.2R3-S5 or later, 21.3R3-S4 or later, 21.4R3-S4 or later, 22.1R3-S4 or later, 22.2R3 or later, 22.3R3 or later, or 22.4R3 or later; for Junos OS Evolved upgrade to 22.3R3-EVO or later, 22.4R3-EVO or later, or 23.2R1-EVO or later
3. Backup the current configuration using 'request system backup' or 'file copy' to a secure location
4. Schedule a maintenance window as the upgrade will require a reboot
5. Download the appropriate Junos software upgrade package from the Juniper support portal
6. Upload the upgrade package to the device using 'request system software add <package>'
7. Reboot the device to apply the upgrade using 'request system reboot'
8. After reboot, verify the new version is running with 'show version'

Caveat Standard Junos upgrade - may require maintenance window as rpd restart causes temporary routing disruption; ensure compatibility with other network devices

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
Testing10.0 h
Review / QA4.0 h

32.0 hours of engineering $5,580

Get the upgrade done

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

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

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2023-44175?

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 existsUpgrade to 20.4 or later

Severity 7.5 High

Exploit likelihood EPSS, next 30 days 0.5%

Affects: Junos

Remediation

A high-priority fix

Fix this in Junos 32 hrs · Moderate

Typical engagement from $5,580

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2023-44175 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