Root access via hardcoded shadow-file password
Published May 9, 2024 · Updated Feb 13, 2025
Hard-coded credentials in TOTOLINK CP450 4.1.0cu.747_B20191224 allow attackers on the adjacent network to log in as root. The firmware ships /etc/shadow.sample with a fixed root password hash whose plaintext is recoverable from the published image. No prior privileges or user interaction are required, and successful authentication grants complete control of the device.
Summary
What happened
Hard-coded credentials in TOTOLINK CP450 4.1.0cu.747_B20191224 allow attackers on the adjacent network to log in as root. The firmware ships /etc/shadow.sample with a fixed root password hash whose plaintext is recoverable from the published image. No prior privileges or user interaction are required, and successful authentication grants complete control of the device.
The record
- CVE
- CVE-2024-34211
- Published
- May 9, 2024
- Updated
- Feb 13, 2025
- Vendor
- TOTOLINK
- Product
- CP450
- Classifications
- CWE-259, T1078
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 9, 2024CVE publishedPublication date reported by the CVE source.
- Feb 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=4.1.0cu.747_b20191224
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.
Public exploit references
- CP450 hard code password for rootproof of concept · demonstrated
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