Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-67305: n/a

0
Critical
VulnerabilityCVE-2025-67305cvecve-2025-67305
Published: Thu Feb 19 2026 (02/19/2026, 00:00:00 UTC)
Source: CVE Database V5

Description

In 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.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/28/2026, 13:32:32 UTC

Technical Analysis

CVE-2025-67305 is a critical security vulnerability affecting RUCKUS Network Director (RND) versions earlier than 4.5.0.56. The root cause is the presence of hardcoded SSH private keys for the 'postgres' user embedded within the OVA appliance image. These keys are identical across all deployments, which means that any attacker with network access to the appliance can use these keys to authenticate via SSH without requiring a password. This bypasses normal authentication mechanisms entirely. Once authenticated, the attacker gains superuser privileges on the PostgreSQL database backend. This level of access allows the attacker to manipulate database contents, including creating new administrative users for the RND web interface, thereby gaining persistent administrative control over the management platform. Further privilege escalation within the appliance or connected infrastructure is also possible. The vulnerability is classified under CWE-321 (Use of Hard-coded Cryptographic Key) and has a CVSS v3.1 base score of 9.8, reflecting its critical impact on confidentiality, integrity, and availability. The attack vector is network-based with no privileges or user interaction required, making exploitation straightforward if network access is available. Although no public exploits have been reported yet, the severity and ease of exploitation make this a high-risk vulnerability requiring immediate attention.

Potential Impact

The impact of CVE-2025-67305 is severe for organizations using vulnerable versions of RUCKUS Network Director. An attacker exploiting this vulnerability can gain unauthorized superuser access to the PostgreSQL database, compromising all stored data and configurations. This includes the ability to create new administrative accounts, effectively taking over the management interface and potentially the entire wireless network infrastructure managed by RND. Such control could lead to network disruptions, data exfiltration, unauthorized configuration changes, and lateral movement within the network. The vulnerability compromises confidentiality, integrity, and availability simultaneously, making it a critical threat to operational continuity and data security. Organizations in sectors relying heavily on wireless network management—such as enterprises, service providers, education, and government—face heightened risks. The lack of required authentication or user interaction lowers the barrier for attackers, increasing the likelihood of exploitation if network access is not properly restricted.

Mitigation Recommendations

To mitigate CVE-2025-67305, organizations should take the following specific actions: 1) Immediately upgrade RUCKUS Network Director to version 4.5.0.56 or later once the vendor releases a patch that removes the hardcoded SSH keys. 2) Until a patch is available, restrict network access to the RND appliance by implementing strict network segmentation and firewall rules that limit SSH and management interface access to trusted administrative hosts only. 3) Conduct an audit of existing RND deployments to identify any unauthorized administrative users or suspicious activity that may indicate exploitation. 4) Rotate all credentials and keys related to the RND environment after patching to invalidate any compromised keys. 5) Monitor network traffic and logs for unusual SSH authentication attempts or database access patterns. 6) Consider deploying intrusion detection/prevention systems (IDS/IPS) to detect exploitation attempts targeting this vulnerability. 7) Educate network and security teams about the risk and ensure incident response plans include steps for handling potential RND compromises. These targeted measures go beyond generic advice by focusing on immediate containment, detection, and remediation specific to the nature of this vulnerability.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
mitre
Date Reserved
2025-12-08T00:00:00.000Z
Cvss Version
null
State
PUBLISHED

Threat ID: 699812af2c4d84f260aeb061

Added to database: 2/20/2026, 7:52:15 AM

Last enriched: 2/28/2026, 1:32:32 PM

Last updated: 4/6/2026, 11:39:17 AM

Views: 79

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses