dbcve.org
Junos Os EvolvedOperating system · Juniper

CVE-2024-21612

HIGH · 7.5 CVSS v3.1 Published 2024-01-12
Fix available
A fix is available. Upgrade to 21.2 or later.
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 Handling of Syntactically Invalid Structure vulnerability in Object Flooding Protocol (OFP) service of Juniper Networks Junos OS Evolved allows an unauthenticated, network-based attacker to cause a Denial of Service (DoS). On all Junos OS Evolved platforms, when specific TCP packets are received on an open OFP port, the OFP crashes leading to a restart of Routine Engine (RE). Continuous receipt of these specific TCP packets will lead to a sustained Denial of Service (DoS) condition. This issue affects: Juniper Networks Junos OS Evolved * All versions earlier than 21.2R3-S7-EVO; * 21.3 versions earlier than 21.3R3-S5-EVO ; * 21.4 versions earlier than 21.4R3-S5-EVO; * 22.1 versions earlier than 22.1R3-S4-EVO; * 22.2 versions earlier than 22.2R3-S3-EVO ; * 22.3 versions earlier than 22.3R3-EVO; * 22.4 versions earlier than 22.4R2-EVO, 22.4R3-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 Juniper Networks Junos OS Evolved's Object Flooding Protocol (OFP) service allows unauthenticated network attackers to crash the OFP process by sending specially crafted TCP packets to an open OFP port. This causes the Routine Engine to restart, and continuous attacks result in sustained DoS.

MitigationApply the vendor-supplied Junos OS Evolved updates (21.2R3-S7-EVO, 21.3R3-S5-EVO, 21.4R3-S5-EVO, 22.1R3-S4-EVO, 22.2R3-S3-EVO, 22.3R3-EVO, 22.4R2-EVO or 22.4R3-EVO or later). As interim mitigation, restrict access to OFP ports via firewall ACLs or network segmentation.

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

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 the device runs Junos OS Evolved
    Execute 'show version' or 'show system information' and look for 'Evolved' in the OS description or model number indicating Evolved platform
    Affected if The device is running Junos OS Evolved (not standard Junos OS)
  2. Identify the installed Junos OS Evolved version
    Run 'show version detail' or 'request system version' to obtain the exact version number such as 21.2, 21.3, 21.4, 22.1, 22.2, 22.3, or 22.4
    Affected if The version matches one in the affected list: any version below 21.2, or exactly 21.2, 21.3, 21.4, 22.1, 22.2, 22.3, or 22.4
  3. Verify if the Object Flooding Protocol (OFP) service is enabled
    Run 'show protocol ofp' or check the OFP service configuration via 'show configuration protocols ofp'
    Affected if OFP is enabled and running on the device
  4. Determine if OFP ports are exposed to untrusted networks
    Review firewall ACLs, port exposure settings, or run 'show system connections' to check if OFP TCP port is listening on external interfaces accessible from untrusted networks
    Affected if OFP service port is reachable from network segments that contain untrusted or external attackers

The environment is affected if the device runs Junos OS Evolved with a version in the affected list and has OFP service enabled and accessible from vulnerable network positions.

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
Upgrade available Upgrade to 21.2 or later
Fixed in 21.2
Interim mitigation

Apply the vendor-supplied Junos OS Evolved updates (21.2R3-S7-EVO, 21.3R3-S5-EVO, 21.4R3-S5-EVO, 22.1R3-S4-EVO, 22.2R3-S3-EVO, 22.3R3-EVO, 22.4R2-EVO or 22.4R3-EVO or later). As interim mitigation, restrict access to OFP ports via firewall ACLs or network segmentation.

Recommended fix High confidence

Upgrade to 21.2R3-S7-EVO, 21.3R3-S5-EVO, 21.4R3-S5-EVO, or a later 22.x release (22.1R3-S4-EVO, 22.2R3-S3-EVO, 22.3R3-EVO, or 22.4R2/22.4R3-EVO)

  1. 1. Identify the current Junos OS Evolved version using 'show version' command
  2. 2. Based on current version, determine the appropriate fixed release from the following: 21.2R3-S7-EVO or later, 21.3R3-S5-EVO or later, 21.4R3-S5-EVO or later, 22.1R3-S4-EVO or later, 22.2R3-S3-EVO or later, 22.3R3-EVO or later, or 22.4R2-EVO/22.4R3-EVO
  3. 3. Review Juniper Networks upgrade documentation and release notes for the target version
  4. 4. Schedule a maintenance window as upgrades require system downtime
  5. 5. Back up current configuration using 'request system configuration backup'
  6. 6. Download the target Junos OS Evolved software from Juniper support portal
  7. 7. Install the upgrade using 'request system software add <package> reboot'
  8. 8. After reboot, verify the new version with 'show version'
Caveat Standard Junos OS Evolved upgrade precautions apply - ensure configuration compatibility, test in lab environment first, and plan for potential rollback

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

Fix this in Junos Os Evolved Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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