Cyber Resilience

CVE-2025-30653

Juniper Junos ≤ 22.2

Published
09 April 2025
Modified
23 January 2026
Patch / advisory
View advisory
CVSS Score v4 6.0
Click a component to see what it means
Raw vectorCVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0024 15th percentile
Risk Priority 33 floored blend · peak EPSS

Summary

CVE-2025-30653 is a medium-severity Expired Pointer Dereference (CWE-825) vulnerability in Juniper Junos. Its CVSS base score is 6.0 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 15th 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 SA-11 (Developer Testing and Evaluation) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

An Expired Pointer Dereference vulnerability in Routing Protocol Daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows an unauthenticated, adjacent attacker to cause Denial of Service (DoS).On all Junos OS and Junos OS Evolved platforms, when an…

more

MPLS Label-Switched Path (LSP) is configured with node-link-protection and transport-class, and an LSP flaps, rpd crashes and restarts. Continuous flapping of LSP can cause a sustained Denial of Service (DoS) condition. This issue affects: Junos OS: * All versions before 22.2R3-S4, * 22.4 versions before 22.4R3-S2, * 23.2 versions before 23.2R2, * 23.4 versions before 23.4R2. Junos OS Evolved: * All versions before 22.2R3-S4-EVO, * 22.4-EVO versions before 22.4R3-S2-EVO, * 23.2-EVO versions before 23.2R2-EVO, * 23.4-EVO versions before 23.4R2-EVO.

CWE(s)
CWE-825

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 →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
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 →
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-2024-30386Same product: Juniper Junos
CVE-2024-30395Same product: Juniper Junos
CVE-2026-21921Same product: Juniper Junos
CVE-2025-30646Same product: Juniper Junos
CVE-2024-39543Same product: Juniper Junos
CVE-2023-44182Same product: Juniper Junos
CVE-2024-39558Same product: Juniper Junos
CVE-2025-30651Same product: Juniper Junos
CVE-2025-52955Same product: Juniper Junos
CVE-2023-28980Same product: Juniper Junos

Affected Assets

juniper
junos
22.2, 22.4, 23.2, 23.4 · ≤ 22.2
juniper
junos os evolved
22.2, 22.4, 23.2, 23.4 · ≤ 22.2

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation (including fuzzing, static analysis, and dynamic memory checkers) directly finds expired-pointer dereferences before deployment.

SA-8 Security and Privacy Engineering Principles partial match

Secure engineering principles applied during design and implementation can mandate memory-safe allocation, ownership, and deallocation patterns that structurally avoid use of expired pointers.

SC-39 Process Isolation partial match

Process isolation confines the effects of a use-after-free within a single address space, reducing cross-process impact.

SI-16 Memory Protection partial match

Memory-protection mechanisms limit the blast radius when an expired pointer is dereferenced, even though they do not stop the coding flaw itself.

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-development practices directly prevent coding errors such as use-after-free while one CWE contributes only modestly to the full control.

ID.AM-08 partial match
prevents

Lifecycle management includes secure development and maintenance phases that reduce memory-safety defects.

ID.RA-01 partial match
prevents

Vulnerability identification processes can discover use-after-free flaws via scanning or analysis.

PR.PS-02 partial match
prevents

Routine patching and replacement can eliminate known instances of expired-pointer bugs.

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 use-after-free issues, but removing this weakness alone does not fulfill the testing control.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle practices can include pointer lifetime and memory-management rules that reduce expired-pointer dereferences.

A.8.26 Application security requirements partial match
prevents

Application security requirements may mandate safe memory handling, but eliminating this single weakness does not satisfy the broader requirement.

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

Secure architecture and engineering principles can prescribe memory-safety patterns, yet fixing only this weakness does not achieve the control.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly address pointer lifetime and deallocation discipline, substantially mitigating expired-pointer dereference.

A.8.32 Change management partial match
prevents

Change-management processes can require re-validation of memory safety after modifications, indirectly reducing the weakness.

References