dbcve.org
JunosOperating system · Juniper

CVE-2024-21614

HIGH · 7.5 CVSS v3.1 Published 2024-01-12
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 Check for Unusual or Exceptional Conditions vulnerability in Routing Protocol Daemon (RPD) of Juniper Networks Junos OS and Junos OS Evolved allows a network-based, unauthenticated attacker to cause rpd to crash, leading to Denial of Service (DoS). On all Junos OS and Junos OS Evolved platforms, when NETCONF and gRPC are enabled, and a specific query is executed via Dynamic Rendering (DREND), rpd will crash and restart. Continuous execution of this specific query will cause a sustained Denial of Service (DoS) condition. This issue affects: Juniper Networks Junos OS * 22.2 versions earlier than 22.2R2-S2, 22.2R3; * 22.3 versions earlier than 22.3R2, 22.3R3. Juniper Networks Junos OS Evolved * 22.2 versions earlier than 22.2R2-S2-EVO, 22.2R3-EVO; * 22.3 versions earlier than 22.3R2-EVO, 22.3R3-EVO. This issue does not affect Juniper Networks: Junos OS versions earlier than 22.2R1; Junos OS Evolved versions earlier than 22.2R1-EVO.

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

A vulnerability in the Routing Protocol Daemon (RPD) of Juniper Networks Junos OS and Junos OS Evolved allows unauthenticated attackers to crash rpd via a specific Dynamic Rendering (DREND) query when NETCONF and gRPC are enabled, causing Denial of Service.

MitigationUpgrade Junos OS/Evolved to a patched version (22.2R2-S2/22.2R3 or later, 22.3R2/22.3R3 or later). Alternatively, disable NETCONF and gRPC if not required to reduce attack surface.

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:= 22.2= 22.3
Junos Os EvolvedOperating system
Affected:= 22.2= 22.3

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. Check Junos OS version
    Run 'show version' or 'show version detail' to identify the installed Junos OS version
    Affected if The version is exactly 22.2 or 22.3 (or any 22.2.x/22.3.x variant in the 22.2R/22.3R release train)
  2. Verify NETCONF is enabled
    Run 'show configuration system services netconf' or check the active NETCONF configuration
    Affected if NETCONF service is enabled (ssh port 830 configured under system services netconf)
  3. Verify gRPC is enabled
    Run 'show configuration system services grpc' or check the active gRPC configuration
    Affected if gRPC service is enabled (grpc configured under system services)
  4. Confirm RPD is running
    Run 'show system processes routing-protocols' or 'show cli authorization' to verify rpd process is active
    Affected if RPD process is currently running (the vulnerability causes rpd to crash when exploited)

You are affected if you are running Junos OS or Junos OS Evolved version 22.2 or 22.3 AND both NETCONF and gRPC services are enabled, as this specific combination allows the unauthenticated DREND query attack to crash rpd.

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/Evolved to a patched version (22.2R2-S2/22.2R3 or later, 22.3R2/22.3R3 or later). Alternatively, disable NETCONF and gRPC if not required to reduce attack surface.

Recommended fix High confidence

22.2R2-S2 or 22.2R3 (Junos OS) / 22.2R2-S2-EVO or 22.2R3-EVO (Junos OS Evolved) / 22.3R2 or 22.3R3 (Junos OS) / 22.3R2-EVO or 22.3R3-EVO (Junos OS Evolved)

  1. 1. Identify the exact current Junos OS or Junos OS Evolved version using 'show version' command
  2. 2. For Junos OS 22.2.x systems: upgrade to 22.2R2-S2 or 22.2R3
  3. 3. For Junos OS 22.3.x systems: upgrade to 22.3R2 or 22.3R3
  4. 4. For Junos OS Evolved 22.2.x systems: upgrade to 22.2R2-S2-EVO or 22.2R3-EVO
  5. 5. For Junos OS Evolved 22.3.x systems: upgrade to 22.3R2-EVO or 22.3R3-EVO
  6. 6. After upgrade, verify rpd is running using 'show system processes routing-daemon'
  7. 7. Confirm NETCONF and gRPC services are functioning normally
Caveat Standard Junos upgrade best practices apply - test in lab environment before production deployment

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-2024-21614 — 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-2024-21614 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