CVE-2025-67305
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 · uneditedIn RUCKUS Network Director (RND) < 4.5.0.56, the OVA appliance contains hardcoded SSH keys for the postgres user. These keys are identical across all deployments, allowing an attacker with network access to authenticate via SSH without a password. Once authenticated, the attacker can access the PostgreSQL database with superuser privileges, create administrative users for the web interface, and potentially escalate privileges further.
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 confidenceRUCKUS Network Director (RND) versions before 4.5.0.56 ship with hardcoded SSH keys for the postgres user in the OVA appliance image. These keys are identical across all deployments, enabling any attacker with network access to authenticate via SSH without credentials. The postgres user has PostgreSQL superuser privileges, allowing the attacker to access the database, create administrative web interface users, and potentially escalate privileges on the underlying system.
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< 4.5.0.56CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Verify RND versionCheck the installed RND version through the web interface (typically in Help > About) or by querying the system. Compare it against the affected range: versions below 4.5.0.56 are vulnerable.Affected if The installed version is below 4.5.0.56
-
Locate the hardcoded postgres SSH private keySearch the filesystem for SSH private keys belonging to the postgres user. In RND OVA appliances, check common locations such as /home/postgres/.ssh/ or within the appliance image files for any private key file.Affected if A static SSH private key for the postgres user exists on the system, especially if it matches known hardcoded keys or appears across multiple deployments
-
Inspect SSH authorized_keys for postgresExamine /home/postgres/.ssh/authorized_keys (or equivalent postgres home directory) to see if any keys are present that should not be there.Affected if The authorized_keys file contains unexpected or unauthorized public keys, or keys that appear hardcoded rather than uniquely generated
-
Check for unauthorized web interface admin accountsLog into the RND web interface and review the admin user list under Administration > Users or Administrators. Also query the PostgreSQL database directly (as the postgres superuser) for unexpected accounts in the admin or user tables.Affected if There are admin accounts in the web interface or database that were not created by your organization, or suspicious accounts with elevated privileges
-
Review SSH authentication logs for postgres login attemptsExamine system logs (/var/log/secure, /var/log/auth.log, or similar) and PostgreSQL logs for unauthorized SSH connections to the postgres account, especially from unexpected IP addresses.Affected if Logs show SSH login successes for the postgres user from sources you do not recognize, or brute force attempts targeting this account
You are affected if your RND version is below 4.5.0.56 and either the hardcoded postgres SSH private key exists on your system or unauthorized admin accounts are present.
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 · scoped4.5.0.56
Upgrade RND to version 4.5.0.56 or later to replace the hardcoded SSH keys. If already deployed, rotate SSH keys, change PostgreSQL credentials, review for unauthorized admin accounts, and audit for post-exploitation activity.
Ruckus Network Director 4.5.0.56 or later
- Perform a full backup of the current Ruckus Network Director installation and database
- Download Ruckus Network Director version 4.5.0.56 or later from the official CommScope webresources portal
- Follow the standard upgrade procedure documented in the RND installation guide
- After upgrading, immediately regenerate or rotate all SSH host keys on the appliance
- Change the default postgres database password and all application default passwords
- Verify that the hardcoded SSH keys have been replaced with unique keys per deployment
- Confirm that the web interface admin credentials have been changed from defaults
- Validate that the PostgreSQL superuser access is properly secured with unique credentials
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-67305 — 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-67305 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