Unauthenticated reboot via DNS rebinding
Published Apr 5, 2024 · Updated Mar 13, 2025
Cross-site request forgery in SpaceX Starlink Gen 2 Router before 2023.53.0 allows remote attackers to reboot the router via DNS rebinding. The management interface accepts browser requests after an attacker-controlled hostname is rebound to its local address, exposing unauthenticated reboot, stow, and speed-test operations. A device connected through Starlink must load the malicious site; authenticated controls such as Wi-Fi password changes and repeater enrollment remain inaccessible.
Summary
What happened
Cross-site request forgery in SpaceX Starlink Gen 2 Router before 2023.53.0 allows remote attackers to reboot the router via DNS rebinding. The management interface accepts browser requests after an attacker-controlled hostname is rebound to its local address, exposing unauthenticated reboot, stow, and speed-test operations. A device connected through Starlink must load the malicious site; authenticated controls such as Wi-Fi password changes and repeater enrollment remain inaccessible.
The record
- CVE
- CVE-2023-52235
- Published
- Apr 5, 2024
- Updated
- Mar 13, 2025
- Vendor
- SpaceX
- Product
- Starlink Gen 2 Router
- Classifications
- CWE-350, T1189
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 5, 2024CVE publishedPublication date reported by the CVE source.
- Mar 13, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <07dd2798-ff15-4722-a9ee-de28928aed34
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo