Remote root access via unauthenticated Telnet enablement
Published Jun 17, 2024 · Updated Jul 9, 2026
Improper privilege management in Jlink AX1800 1.0 allows remote attackers to gain root access through an unauthenticated Telnet API. The /web/um_telnet_set handler accepts requests without a password, enables Telnet, and sets credentials that permit a subsequent su command to open a root shell. Remote network access alone is sufficient, and successful exploitation grants command execution with full device privileges.
Summary
What happened
Improper privilege management in Jlink AX1800 1.0 allows remote attackers to gain root access through an unauthenticated Telnet API. The /web/um_telnet_set handler accepts requests without a password, enables Telnet, and sets credentials that permit a subsequent su command to open a root shell. Remote network access alone is sufficient, and successful exploitation grants command execution with full device privileges.
The record
- CVE
- CVE-2023-37058
- Published
- Jun 17, 2024
- Updated
- Jul 9, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-269, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 17, 2024CVE publishedPublication date reported by the CVE source.
- Jul 9, 2026Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- Jlink Router RCE proof of conceptproof 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