Summary
KAYSUS KS-WR3600 routers running firmware 1.0.5.9.1 expose an SSH service on the LAN interface with the root account configured to have no password and no option for administrators to disable SSH or require authentication.
Any attacker with network access to the LAN segment can obtain an unauthenticated root shell and execute arbitrary commands with full privileges on the device.
Affected context
This vulnerability affects KAYSUS KS-WR3600 routers with firmware version 1.0.5.9.1 where:
- The SSH service is enabled by default and bound to the LAN interface.
- The built-in
rootaccount has no password configured. - Administrators cannot disable SSH or configure authentication through either the web GUI or CLI.
In typical deployments, any device on the same internal network segment as the router can reach the exposed SSH port and interact with the unauthenticated root shell.
Exploit preconditions
- Attack surface: SSH service listening on the router's LAN interface.
- Required access: Network adjacency to the LAN (e.g., connected client, malicious insider, compromised IoT/endpoint on the LAN).
- User interaction: No user interaction is required; the attacker directly connects to the SSH port.
- Authentication requirements: None; the root account has no password and no enforced authentication.
- Why exploitation is possible: The system fails to enforce authentication for a privileged account (CWE-306) and applies overly permissive access control on a high-privilege service (CWE-284), combined with a default credential state equivalent to an empty password (CWE-521).
Why this happens
The core issue is a combination of missing authentication and insecure default configuration on a high-privilege service.
The SSH daemon is exposed on the LAN interface with a root account that has no password, and the device firmware provides no administrative controls to disable SSH or enforce proper authentication.
This maps to:
- CWE-306 (Missing Authentication for Critical Function): SSH access to a root shell is a critical function that is made available without any authentication checks.
- CWE-284 (Improper Access Control): The router does not restrict who can invoke the SSH service from the LAN, effectively granting root access to any reachable host.
- CWE-521 (Weak Password Requirements): The use of an empty password for the root account reflects an absence of password policy and secure default credentials.
Abstractly, the insecure pattern is exposing administrative interfaces with full privileges using either no authentication or trivially bypassed controls, without giving operators the ability to harden or disable those interfaces.
Potential impact
- An attacker on the LAN can obtain an unauthenticated root shell on the router.
- Full control of router configuration, including DNS, routing, firewall, and NAT rules.
- Installation of persistent malware or backdoors on the router.
- Interception, modification, or redirection of network traffic (e.g., man-in-the-middle attacks).
- Use of the compromised router as a pivot point for attacking other internal devices.
- Participation of the router in botnets, DDoS attacks, or other malicious campaigns.
General mitigation guidance
In the absence of fine-grained controls on the affected firmware, mitigation strategies focus on restricting access and enforcing defense-in-depth around the exposed SSH service:
- Network segmentation: Place the router in a network segment where only trusted administration hosts can reach its LAN IP and SSH port, using VLANs or separate management networks.
- External access controls: Use upstream firewalls, host-based firewalls, or switch ACLs to limit which IP addresses can connect to the router's SSH port.
- Physical and logical access restriction: Limit who can physically connect to LAN ports or join the Wi-Fi network associated with the vulnerable router.
- Privileged isolation: Treat the router as a high-risk asset and avoid connecting untrusted or unmanaged devices to the same LAN segment.
- Configuration hardening where possible: If any partial control exists (e.g., port forwarding, ACLs, or service binding), use it to narrow exposure of SSH, even if it cannot be fully disabled.
- Secure-by-default procurement: For future deployments, favor network equipment that allows administrators to disable remote management services, configure strong credentials, and enforce robust authentication policies out of the box.
How teams detect issues like this
Detection can combine network-level observation with configuration and firmware analysis:
- Network scanning and inventory: Regularly scan internal networks to identify management services (SSH, Telnet, HTTP/HTTPS) exposed by infrastructure devices and verify their authentication posture.
- Configuration review: During routine audits, confirm which remote management interfaces are enabled on routers and whether strong authentication is configured and enforced.
- Traffic monitoring: Use IDS/IPS or network monitoring to flag unusual SSH access patterns to routers, particularly from new or untrusted hosts.
- Policy-based checks: Implement internal security baselines that prohibit devices with non-configurable default admin accounts or non-disablable remote management services from being deployed in sensitive environments.
- Firmware and asset management: Track firmware versions and device models in an asset inventory system to identify where insecure defaults may exist and prioritize them for containment or replacement.

