dbcve.org
JunosOperating system · Juniper

CVE-2025-52963

MEDIUM · 5.5 CVSS v3.1 Published 2025-07-11
Fix available
A fix is available. Upgrade to 21.2 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An Improper Access Control vulnerability in the User Interface (UI) of Juniper Networks Junos OS allows a local, low-privileged attacker to bring down an interface, leading to a Denial-of-Service. Users with "view" permissions can run a specific request interface command which allows the user to shut down the interface. This issue affects Junos OS:  * All versions before 21.2R3-S9, * from 21.4 before 21.4R3-S11, * from 22.2 before 22.2R3-S7, * from 22.4 before 22.4R3-S7, * from 23.2 before 23.2R2-S4, * from 23.4 before 23.4R2-S5,   * from 24.2 before 24.2R2-S1, * from 24.4 before 24.4R1-S3, 24.4R2.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Juniper Junos OS contains improper access control in the UI that allows users with only 'view' (read-only) permissions to execute a privileged 'request interface' command that can shut down network interfaces, causing denial of service. This bypasses the intended permission model where view-only users should not be able to modify interface state.

MitigationUpgrade Junos OS to one of the fixed versions: 21.2R3-S9, 21.4R3-S11, 22.2R3-S7, 22.4R3-S7, 23.2R2-S4, 23.4R2-S5, 24.2R2-S1, 24.4R1-S3, or 24.4R2.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
JunosOperating system
Affected:< 21.2= 21.2= 21.4= 22.2= 22.4= 23.2= 23.4= 24.2= 24.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed Junos OS version
    Run 'show version' or 'show version detail' via CLI to obtain the exact Junos version number
    Affected if The installed version matches one of the affected versions: < 21.2, 21.2, 21.4, 22.2, 22.4, 23.2, 23.4, 24.2, or 24.4 (not including the fixed sub-versions like 21.2R3-S9)
  2. Confirm user permission levels configured
    Run 'show system login' or 'show configuration system login' to list all user accounts and their permission classes (such as 'view-only', 'operator', 'super-user')
    Affected if Any user account is assigned a 'view' or 'read-only' permission class
  3. Check if web UI (J-Web) is enabled
    Run 'show configuration system services web-management' to see if the web-based UI is enabled
    Affected if Web-management services are enabled on the device
  4. Verify the vulnerability exists by testing command access
    Using a test account with only 'view' (read-only) permissions, attempt to execute 'request interface interface-name offline' or 'request interface interface-name disable' via the CLI or web UI
    Affected if The command executes successfully without permission error, allowing a view-only user to shut down an interface

A device is affected if it runs any of the listed vulnerable Junos versions AND has view-only users configured AND the 'request interface' shutdown command is accessible to those restricted users, allowing unauthorized interface state changes.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 21.2 or later
Fixed in 21.2
Interim mitigation

Upgrade Junos OS to one of the fixed versions: 21.2R3-S9, 21.4R3-S11, 22.2R3-S7, 22.4R3-S7, 23.2R2-S4, 23.4R2-S5, 24.2R2-S1, 24.4R1-S3, or 24.4R2.

Recommended fix High confidence

Upgrade to 21.2R3-S9 or later (21.4 branch), 22.2R3-S7 or later, 22.4R3-S7 or later, 23.2R2-S4 or later, 23.4R2-S5 or later, 24.2R2-S1 or later, or 24.4R1-S3/24.4R2 or later - select the appropriate train for your hardware platform

  1. 1. Identify the current Junos OS version running on the device using 'show version'
  2. 2. Review the version against the affected ranges: before 21.2R3-S9, 21.4R1-R3-S10, 22.2R1-R3-S6, 22.4R1-R3-S6, 23.2R1-R2-S3, 23.4R1-R2-S4, 24.2R1-R2, 24.4R1 before R1-S3
  3. 3. Plan maintenance window as upgrade requires device reboot
  4. 4. Download the appropriate fixed release for your hardware platform from Juniper Networks
  5. 5. Upload the Junos upgrade image to the device
  6. 6. Run 'request system software add <package> reboot' to upgrade and reboot
  7. 7. After reboot, verify new version using 'show version'
  8. 8. Confirm fix by testing that users with 'view' permissions can no longer execute 'request interface <name> shutdown' command
Caveat Standard Junos upgrade may cause brief downtime; ensure configuration compatibility review before upgrade; some legacy interface commands may have changed

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Junos Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-52963 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-52963 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data