Cyber Resilience

CVE-2025-52983

Juniper Junos ≤ 22.2

Published
11 July 2025
Modified
17 June 2026
Patch / advisory
View advisory
CVSS Score v4 8.6
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/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:U/V:X/RE:M/U:X
EPSS Score 0.0060 46th percentile
Risk Priority 31 floored blend · peak EPSS

Summary

CVE-2025-52983 is a high-severity UI Discrepancy for Security Feature (CWE-446) vulnerability in Juniper Junos. Its CVSS base score is 8.6 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Subvert Trust Controls (T1553); 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

A UI Discrepancy for Security Feature vulnerability in the UI of Juniper Networks Junos OS on VM Host systems allows a network-based, unauthenticated attacker to access the device. On VM Host Routing Engines (RE), even if the configured public key…

more

for root has been removed, remote users which are in possession of the corresponding private key can still log in as root. This issue affects Junos OS: * all versions before 22.2R3-S7, * 22.4 versions before 22.4R3-S5, * 23.2 versions before 23.2R2-S3, * 23.4 versions before 23.4R2-S3, * 24.2 versions before 24.2R1-S2, 24.2R2.

CWE(s)
CWE-446

Related Threats

MITRE ATT&CK Enterprise Techniques

T1553 Subvert Trust Controls Defense Impairment
Adversaries may undermine security controls that will either warn users of untrusted activity or prevent execution of untrusted programs.
attack.mitre.org →
T1557 Adversary-in-the-Middle Credential Access
Adversaries may attempt to position themselves between two or more networked devices using an adversary-in-the-middle (AiTM) technique to support follow-on behaviors such as [Network Sniffing](https://attack.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-28963Same product: Juniper Junos
CVE-2023-28962Same product: Juniper Junos
CVE-2025-52951Same product: Juniper Junos
CVE-2023-22395Same product: Juniper Junos
CVE-2024-21600Same product: Juniper Junos
CVE-2023-36842Same product: Juniper Junos
CVE-2023-22399Same product: Juniper Junos
CVE-2024-21617Same product: Juniper Junos
CVE-2023-36841Same product: Juniper Junos
CVE-2025-52948Same product: Juniper Junos

Affected Assets

juniper
junos
22.2, 22.4, 23.2, 23.4, 24.2 · ≤ 22.2

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 2 hardening rules · 1 OS baseline
Validate
Prove the fix (OWASP ASVS)

—

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 accurate UI representation of security configuration state.

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 and acceptance can detect UI discrepancies before release, providing strong mitigation for this weakness.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle requires UI security features to be correctly implemented and verified, directly preventing misleading security-state feedback.

A.8.26 Application security requirements partial match
prevents

Application security requirements should specify correct UI behavior for security controls, reducing the chance of misleading user feedback.

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

Secure architecture principles can guide UI design but do not specifically address misleading security-state indicators.

A.8.28 Secure coding partial match
prevents

Secure coding practices help avoid implementation bugs that cause UI discrepancies, though the control is not focused on UI correctness.

A.8.5 Secure authentication none match
none

Secure authentication control may be undermined by UI discrepancies, but eliminating the weakness does not implement the authentication mechanism itself.

References