Cyber Resilience

CVE-2023-22412

Juniper Junos 20.4 … 22.1

Published
13 January 2023
Modified
21 November 2024
Patch / advisory
View 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.0047 38th percentile
Risk Priority 57 floored blend · peak EPSS

Summary

CVE-2023-22412 is a high-severity Improper Locking (CWE-667) vulnerability in Juniper Junos. Its CVSS base score is 7.5 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Endpoint Denial of Service (T1499); ranked at the 38th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

EU & UK References

Vulnerability Data

An Improper Locking vulnerability in the SIP ALG of Juniper Networks Junos OS on MX Series with MS-MPC or MS-MIC card and SRX Series allows an unauthenticated, network-based attacker to cause a flow processing daemon (flowd) crash and thereby a…

more

Denial of Service (DoS). Continued receipt of these specific packets will cause a sustained Denial of Service condition. This issue occurs when SIP ALG is enabled and specific SIP messages are processed simultaneously. This issue affects: Juniper Networks Junos OS on MX Series and SRX Series 20.4 versions prior to 20.4R3-S4; 21.1 versions prior to 21.1R3-S3; 21.2 versions prior to 21.2R3-S2; 21.3 versions prior to 21.3R3; 21.4 versions prior to 21.4R3; 22.1 versions prior to 22.1R2. This issue does not affect Juniper Networks Junos OS versions prior to 20.4R1 on MX Series, or SRX Series.

CWE(s)
CWE-667

Related Threats

MITRE ATT&CK Enterprise Techniques

T1499 Endpoint Denial of Service Impact
Adversaries may perform Endpoint Denial of Service (DoS) attacks to degrade or block the availability of services to users.
attack.mitre.org →
T1499.004 Application or System Exploitation Impact
Adversaries may exploit software vulnerabilities that can cause an application or system to crash and deny availability to users.
attack.mitre.org →
T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
T1548 Abuse Elevation Control Mechanism Privilege Escalation
Adversaries may circumvent mechanisms designed to control privilege elevation to gain higher-level permissions.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-21914Same product: Juniper Junos
CVE-2023-22409Same product: Juniper Junos
CVE-2023-22416Same product: Juniper Junos
CVE-2023-22394Same product: Juniper Junos
CVE-2023-22404Same product: Juniper Junos
CVE-2023-22415Same product: Juniper Junos
CVE-2023-28985Same product: Juniper Junos
CVE-2024-39540Same product: Juniper Junos
CVE-2023-36831Same product: Juniper Junos
CVE-2023-22417Same product: Juniper Junos

Affected Assets

juniper
junos
20.4, 21.1, 21.2, 21.3, 21.4

Mitigating Controls

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 include code reviews, static analysis, and concurrency standards that prevent improper locking.

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.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect race conditions and locking errors before release.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle includes concurrency and locking requirements that reduce improper locking defects.

A.8.26 Application security requirements partial match
prevents

Application security requirements can mandate proper lock acquisition/release patterns.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles address thread-safety and resource synchronization.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly prohibit missing or incorrect lock usage.

A.8.32 Change management partial match
prevents

Change management may catch locking issues introduced by modifications but does not prevent the weakness itself.

References