dbcve.org
Junos Os EvolvedOperating system · Juniper

CVE-2024-21602

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
A NULL Pointer Dereference vulnerability in Juniper Networks Junos OS Evolved on ACX7024, ACX7100-32C and ACX7100-48L allows an unauthenticated, network-based attacker to cause a Denial of Service (DoS). If a specific IPv4 UDP packet is received and sent to the Routing Engine (RE) packetio crashes and restarts which causes a momentary traffic interruption. Continued receipt of such packets will lead to a sustained DoS. This issue does not happen with IPv6 packets. This issue affects Juniper Networks Junos OS Evolved on ACX7024, ACX7100-32C and ACX7100-48L: * 21.4-EVO versions earlier than 21.4R3-S6-EVO; * 22.1-EVO versions earlier than 22.1R3-S5-EVO; * 22.2-EVO versions earlier than 22.2R2-S1-EVO, 22.2R3-EVO; * 22.3-EVO versions earlier than 22.3R2-EVO. This issue does not affect Juniper Networks Junos OS Evolved versions earlier than 21.4R1-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 NULL Pointer Dereference in packetio on Juniper ACX7024, ACX7100-32C, and ACX7100-48L allows unauthenticated network attackers to crash the Routing Engine by sending a specific IPv4 UDP packet. The packetio process restarts momentarily and repeated packets cause sustained DoS.

MitigationUpgrade Junos OS Evolved to the fixed versions: 21.4R3-S6-EVO, 22.1R3-S5-EVO, 22.2R2-S1-EVO/22.2R3-EVO, or 22.3R2-EVO as appropriate for the hardware platform.

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
Junos Os EvolvedOperating system
Affected:= 21.4= 22.1= 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. Confirm hardware model
    Run `show chassis hardware` or `show system information` to identify the device model
    Affected if Model is ACX7024, ACX7100-32C, or ACX7100-48L (these are the affected platforms)
  2. Check Junos OS Evolved version
    Run `show version` to display the installed Junos OS Evolved version
    Affected if Version begins with 21.4, 22.1, 22.2, or 22.3 (without the S6/S5/S1 patch suffix that indicates the fix)
  3. Verify patch status
    Compare your full version string against the fixed releases: 21.4R3-S6-EVO, 22.1R3-S5-EVO, 22.2R2-S1-EVO, 22.2R3-EVO, or 22.3R2-EVO
    Affected if Running an unpatched version within 21.4, 22.1, 22.2, or 22.3 branches and not yet upgraded to one of the fixed builds

You are affected if your device is an ACX7024, ACX7100-32C, or ACX7100-48L running Junos OS Evolved version 21.4, 22.1, 22.2, or 22.3 without the vendor-supplied security patch.

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 the fixed versions: 21.4R3-S6-EVO, 22.1R3-S5-EVO, 22.2R2-S1-EVO/22.2R3-EVO, or 22.3R2-EVO as appropriate for the hardware platform.

Recommended fix High confidence

21.4R3-S6-EVO, 22.1R3-S5-EVO, 22.2R2-S1-EVO/22.2R3-EVO, or 22.3R2-EVO (depending on current branch)

  1. 1. Identify the current Junos OS Evolved version running on the affected device (ACX7024, ACX7100-32C, or ACX7100-48L).
  2. 2. Based on the current version, upgrade to the minimum fixed release: for 21.4-EVO upgrade to 21.4R3-S6-EVO or later; for 22.1-EVO upgrade to 22.1R3-S5-EVO or later; for 22.2-EVO upgrade to 22.2R2-S1-EVO or 22.2R3-EVO or later; for 22.3-EVO upgrade to 22.3R2-EVO or later.
  3. 3. Download the appropriate upgrade package from the Juniper Networks support portal.
  4. 4. Follow standard Junos OS Evolved upgrade procedures, ensuring to back up the current configuration.
  5. 5. After upgrade, verify the packetio process is running normally and confirm the Junos OS Evolved version matches the fixed release.

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

Fix this in Junos Os Evolved Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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