Telnet service crash via malformed command sequence
Published Feb 10, 2021 · Updated Aug 3, 2024
Improper input validation in FiberHome HG6245D firmware through RP2613 allows remote attackers to crash the CLI telnet daemon. The /fh/extend/load_cli process segfaults after parsing a 13-byte Telnet sequence containing the enable command and control bytes. The service requires enablement for IPv4 access but is exposed over IPv6 by default; exploitation stops Telnet connections without rebooting the router.
Summary
What happened
Improper input validation in FiberHome HG6245D firmware through RP2613 allows remote attackers to crash the CLI telnet daemon. The /fh/extend/load_cli process segfaults after parsing a 13-byte Telnet sequence containing the enable command and control bytes. The service requires enablement for IPv4 access but is exposed over IPv6 by default; exploitation stops Telnet connections without rebooting the router.
The record
- CVE
- CVE-2021-27179
- Published
- Feb 10, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-20, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 10, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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?
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
- crash-auth-telnet proof of conceptfunctional · 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