Cyber Resilience

CVE-2024-21612

Juniper Junos Os Evolved ≤ 21.2

Published
12 January 2024
Modified
17 June 2026
Patch / advisory
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.0053 42th percentile
Risk Priority 58 floored blend · peak EPSS

Summary

CVE-2024-21612 is a high-severity Improper Handling of Syntactically Invalid Structure (CWE-228) vulnerability in Juniper Junos Os Evolved. Its CVSS base score is 7.5 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 42th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

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…

more

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.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-47495Same product: Juniper Junos Os Evolved
CVE-2023-22402Same product: Juniper Junos Os Evolved
CVE-2024-21590Same product: Juniper Junos Os Evolved
CVE-2026-21911Same product: Juniper Junos Os Evolved
CVE-2024-39513Same product: Juniper Junos Os Evolved
CVE-2024-39534Same product: Juniper Junos Os Evolved
CVE-2024-39520Same product: Juniper Junos Os Evolved
CVE-2023-28983Same product: Juniper Junos Os Evolved
CVE-2024-39523Same product: Juniper Junos Os Evolved
CVE-2025-52954Same product: Juniper Junos Os Evolved

Affected Assets

juniper
junos os evolved
21.2, 21.3, 21.4, 22.1, 22.2 · ≤ 21.2

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SI-10 requires validity checks on information inputs, directly stopping syntactically malformed data from being processed without proper handling.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require robust input validation and syntax handling to prevent malformed-structure flaws.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing can detect malformed-input issues but does not itself implement the handling logic.

prevents

Secure development life cycle mandates input validation and error handling that directly prevents improper handling of syntactically invalid structures.

prevents

Application security requirements include explicit rules for input validation and malformed-data handling.

prevents

Secure system architecture principles encourage robust input handling but do not prescribe the specific coding practice.

prevents

Secure coding explicitly requires validation of all input syntax and structure, directly eliminating CWE-228.

References