Telnet access via hard-coded product.ini credential
Published Jul 28, 2024 · Updated Aug 1, 2024
Hard-coded credentials in the TOTOLINK A3600R 4.1.2cu.5182_B20201102 Telnet service allow attackers to authenticate over an adjacent network. /web_cste/cgi-bin/product.ini stores a fixed Telnet credential instead of requiring a device-specific secret. The Telnet service must be reachable from an adjacent network, and public sources do not describe the commands or data available after login.
Summary
What happened
Hard-coded credentials in the TOTOLINK A3600R 4.1.2cu.5182_B20201102 Telnet service allow attackers to authenticate over an adjacent network. /web_cste/cgi-bin/product.ini stores a fixed Telnet credential instead of requiring a device-specific secret. The Telnet service must be reachable from an adjacent network, and public sources do not describe the commands or data available after login.
The record
- CVE
- CVE-2024-7159
- Published
- Jul 28, 2024
- Updated
- Aug 1, 2024
- Vendor
- TOTOLINK
- Product
- A3600R
- Classifications
- CWE-259, T1078.001
- Attack vector
- adjacent
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 28, 2024CVE publishedPublication date reported by the CVE source.
- Aug 1, 2024Record 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.2cu.5182_B20201102
What conditions does exploitation require?
What is affected?
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
- A3600R product.ini proof of conceptproof of concept · unverified
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