Cyber Resilience

CVE-2023-22394

Juniper Junos ≤ 19.3

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.0062 46th percentile
Risk Priority 58 floored blend · peak EPSS

Summary

CVE-2023-22394 is a high-severity Improper Update of Reference Count (CWE-911) vulnerability in Juniper Junos. Its CVSS base score is 7.5 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 46th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

EU & UK References

Vulnerability Data

An Improper Handling of Unexpected Data Type vulnerability in the handling of SIP calls in Juniper Networks Junos OS on SRX Series and MX Series platforms allows an attacker to cause a memory leak leading to Denial of Services (DoS).…

more

This issue occurs on all MX Series platforms with MS-MPC or MS-MIC card and all SRX Series platforms where SIP ALG is enabled. Successful exploitation of this vulnerability prevents additional SIP calls and applications from succeeding. The SIP ALG needs to be enabled, either implicitly / by default or by way of configuration. To confirm whether SIP ALG is enabled on SRX use the following command: user@host> show security alg status | match sip SIP : Enabled This issue affects Juniper Networks Junos OS on SRX Series and on MX Series: All versions prior to 19.3R3-S7; 19.4 versions prior to 19.4R2-S8, 19.4R3-S10; 20.1 versions 20.1R1 and later versions; 20.2 versions prior to 20.2R3-S6; 20.3 versions prior to 20.3R3-S6; 20.4 versions prior to 20.4R3-S5; 21.1 versions prior to 21.1R3-S5; 21.2 versions prior to 21.2R3-S1; 21.3 versions prior to 21.3R3; 21.4 versions prior to 21.4R2-S2, 21.4R3; 22.1 versions prior to 22.1R1-S2, 22.1R2, 22.1R3-S1. This issue does not affect Juniper Networks Junos OS on SRX Series and on MX Series: All versions prior to 18.2R1.

CWE(s)
CWE-911NVD-CWE-Other

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
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.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
attack.mitre.org →
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-22416Same product: Juniper Junos
CVE-2023-22409Same product: Juniper Junos
CVE-2023-22404Same product: Juniper Junos
CVE-2023-22415Same product: Juniper Junos
CVE-2023-22412Same product: Juniper Junos
CVE-2023-28985Same product: Juniper Junos
CVE-2023-36838Same product: Juniper Junos
CVE-2023-22411Same product: Juniper Junos
CVE-2024-39529Same product: Juniper Junos
CVE-2023-36831Same product: Juniper Junos

Affected Assets

juniper
junos
19.3, 19.4, 20.1, 20.2, 20.3 · ≤ 19.3

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 prevent reference-count coding errors via reviews, static analysis, and testing.

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 in development can detect reference-count defects before release, providing partial mitigation.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle practices can include reference-counting rules and automated checks that reduce the likelihood of improper updates.

A.8.26 Application security requirements partial match
prevents

Application security requirements can mandate correct resource-lifetime management, indirectly addressing reference-count errors.

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

Secure system architecture principles encourage explicit resource-ownership models that mitigate reference-count misuse.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly prescribe correct increment/decrement patterns, covering most instances of this weakness.

A.8.32 Change management partial match
prevents

Change-management processes may catch reference-count issues introduced by modifications, but do not address the root coding flaw.

References