dbcve.org
JunosOperating system · Juniper

CVE-2025-30654

MEDIUM · 5.5 CVSS v3.1 Published 2025-04-09
Fix available
A fix is available. Upgrade to 21.4 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 Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the User Interface (UI) of Juniper Networks Junos OS and Junos OS Evolved allows a local, low-privileged, authenticated attacker with access to the CLI to access sensitive information.  Through the execution of a specific show mgd command, a user with limited permissions (e.g., a low-privileged login class user) can access sensitive information such as hashed passwords, that can be used to further impact the system. This issue affects Junos OS:  * All versions before 21.4R3-S10, * from 22.2 before 22.2R3-S5, * from 22.4 before 22.4R3-S5,  * from 23.2 before 23.2R2-S3,  * from 23.4 before 23.4R2-S3. Junos OS Evolved:  * All versions before 21.4R3-S10-EVO, * from 22.2-EVO before 22.2R3-S6-EVO,  * from 22.4-EVO before 22.4R3-S5-EVO,  * from 23.2-EVO before 23.2R2-S3-EVO,  * from 23.4-EVO before 23.4R2-S3-EVO.

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

A vulnerability in Junos OS and Junos OS Evolved allows a low-privileged, authenticated local attacker with CLI access to execute a specific 'show mgd' command that exposes sensitive information, including hashed passwords. The mgd (management daemon) fails to properly enforce permission boundaries, permitting users with limited login class permissions to access data they should not be authorized to view.

MitigationApply the appropriate Junos OS or Junos OS Evolved patch version for your release train as specified in the advisory (e.g., 21.4R3-S10, 22.2R3-S5, 22.4R3-S5, 23.2R2-S3, or 23.4R2-S3). Prior to patching, restrict CLI access for low-privileged users and audit existing user accounts with limited permissions.

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.4= 21.4= 22.2= 22.4= 23.2= 23.4
Junos Os EvolvedOperating system
Affected:< 21.4= 21.4= 22.2= 22.4= 23.2= 23.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
High
Integrity
None
Availability
None

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

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 Junos OS version
    Run 'show version' or 'show version detail' from the CLI to retrieve the installed Junos OS or Junos OS Evolved version.
    Affected if The installed version matches one of the affected ranges: < 21.4, 21.4, 22.2, 22.4, 23.2, or 23.4.
  2. Review user login class permissions
    Run 'show configuration system login' and 'show configuration system login class' to identify users assigned to restricted login classes and their associated permissions.
    Affected if There exist users with limited login class permissions who have CLI access.
  3. Test for vulnerable command exposure
    As a low-privileged user with limited CLI permissions, attempt to run 'show mgd' and inspect the output for sensitive information such as hashed passwords or unauthorized data.
    Affected if The command executes successfully and displays hashed passwords or other sensitive data that should not be accessible to the user's privilege level.
  4. Audit mgd daemon access controls
    Review the mgd (management daemon) configuration and permissions by examining system logs and running 'show log messages' for any unauthorized access attempts to mgd-related commands.
    Affected if Logs indicate that low-privileged users have accessed mgd data they were not authorized to view.

You are affected if your Junos OS/Evolved version is in the vulnerable range AND low-privileged users with CLI access can execute 'show mgd' to view hashed passwords or other sensitive data.

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.4 or later
Fixed in 21.4
Interim mitigation

Apply the appropriate Junos OS or Junos OS Evolved patch version for your release train as specified in the advisory (e.g., 21.4R3-S10, 22.2R3-S5, 22.4R3-S5, 23.2R2-S3, or 23.4R2-S3). Prior to patching, restrict CLI access for low-privileged users and audit existing user accounts with limited permissions.

Recommended fix High confidence

Upgrade to the appropriate S-release: 21.4R3-S10 or later, 22.2R3-S5 or later, 22.4R3-S5 or later, 23.2R2-S3 or later, or 23.4R2-S3 or later for Junos OS; 21.4R3-S10-EVO or later, 22.2R3-S6-EVO or later, 22.4R3-S5-EVO or later, 23.2R2-S3-EVO or later, or 23.4R2-S3-EVO or later for Junos OS Evolved

  1. 1. Identify the current Junos OS or Junos OS Evolved version and branch running on the device using: show version
  2. 2. Based on the current branch, determine the minimum fixed S-release version required (21.4R3-S10, 22.2R3-S5, 22.4R3-S5, 23.2R2-S3, or 23.4R2-S3 for Junos OS; 21.4R3-S10-EVO, 22.2R3-S6-EVO, 22.4R3-S5-EVO, 23.2R2-S3-EVO, or 23.4R2-S3-EVO for Junos OS Evolved)
  3. 3. Download the appropriate fixed Junos software package from the Juniper Networks support portal
  4. 4. Upload the software package to the device using file copy or USB
  5. 5. Install the software upgrade using: request system software add <package-name>
  6. 6. Reboot the device after installation using: request system reboot
  7. 7. After reboot, verify the new version is installed using: show version and confirm the fix is applied
Caveat S-release upgrades are typically non-disruptive on supported hardware but require a reboot; ensure proper change control and maintenance window are scheduled

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

Fix this in Junos Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-30654 — 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-30654 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