CVE-2025-21592
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 · uneditedAn Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the command-line interface (CLI) of Juniper Networks Junos OS on SRX Series devices allows a local, low-privileged user with access to the Junos CLI to view the contents of sensitive files on the file system. Through the execution of either 'show services advanced-anti-malware' or 'show services security-intelligence' command, a user with limited permissions (e.g., a low privilege login class user) can access protected files that should not be accessible to the user. These files may contain sensitive information that can be used to cause further impact to the system. This issue affects Junos OS SRX Series: * All versions before 21.4R3-S8, * from 22.2 before 22.2R3-S5, * from 22.3 before 22.3R3-S3, * from 22.4 before 22.4R3-S2, * from 23.2 before 23.2R2-S1, * from 23.4 before 23.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 confidenceA local information disclosure vulnerability in Juniper Junos OS SRX Series allows low-privileged CLI users to access protected sensitive files through the 'show services advanced-anti-malware' or 'show services security-intelligence' commands. The commands improperly expose file system contents that should be restricted to privileged users.
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< 21.4= 21.4= 22.2= 22.3= 22.4= 23.2= 23.4CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelRun 'show chassis hardware' or 'show version' to confirm the device is an SRX Series applianceAffected if The device is an SRX Series model and the Junos version matches affected versions listed below
-
Check the installed Junos OS versionRun 'show version' and note the exact Junos version (for example, 22.3R1.10)Affected if The installed version is any of: < 21.4, 21.4 (any release), 22.2 (any release), 22.3 (any release), 22.4 (any release), 23.2 (any release), or 23.4 (any release)
-
Verify low-privilege user accounts existRun 'show system users' or check the authentication database for accounts with operator or read-only privilege levels (not root/administrator)Affected if There are non-root users with limited CLI privileges configured on the device
-
Test for exposure via advanced-anti-malware commandAs a low-privilege user (non-root), execute 'show services advanced-anti-malware' and examine the output for any file system paths or sensitive content that should be restrictedAffected if The command returns file system contents, paths to protected files, or sensitive information that should not be visible to non-privileged users
-
Test for exposure via security-intelligence commandAs a low-privilege user (non-root), execute 'show services security-intelligence' and examine the output for any file system paths or sensitive content that should be restrictedAffected if The command returns file system contents, paths to protected files, or sensitive information that should not be visible to non-privileged users
A user is affected if they are running Junos OS on an SRX Series device at any of the affected versions listed and have low-privilege users who can run these show commands and see restricted file system contents.
Generated from the published advisory. Verify against your own configuration.
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 · scoped21.4
Apply the vendor-supplied Junos OS patches for the affected version branches (21.4R3-S8, 22.2R3-S5, 22.3R3-S3, 22.4R3-S2, 23.2R2-S1, or 23.4R2 and later). Until patched, restrict low-privilege user access to these CLI commands.
Upgrade to 21.4R3-S8 / 22.2R3-S5 / 22.3R3-S3 / 22.4R3-S2 / 23.2R2-S1 / 23.4R2 (depending on your current branch)
- 1. Identify current Junos OS version on the SRX device using 'show version' command
- 2. Determine the appropriate fixed release based on current version: for 21.4.x upgrade to 21.4R3-S8 or later; for 22.2.x upgrade to 22.2R3-S5 or later; for 22.3.x upgrade to 22.3R3-S3 or later; for 22.4.x upgrade to 22.4R3-S2 or later; for 23.2.x upgrade to 23.2R2-S1 or later; for 23.4.x upgrade to 23.4R2 or later
- 3. Review Juniper SRX upgrade guide and release notes for compatibility requirements
- 4. Backup current configuration using 'request system configuration rescue save'
- 5. Schedule maintenance window as this upgrade requires device reboot
- 6. Upload the fixed Junos OS image to the device
- 7. Execute upgrade using 'request system software add <package-name> reboot'
- 8. After reboot, verify new version is installed using 'show version'
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-21592 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-21592 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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