Unauthenticated service interruption via unchecked Telnet response buffering
Published Aug 10, 2021 · Updated Aug 4, 2024
Buffer overflow in the Contiki 3.0 Telnet service allows remote attackers to interrupt the service by listing many long file names. Telnet command handling stores all ls output in a fixed-length response buffer without checking whether each write succeeds, so output is lost after the buffer fills. Exploitation requires a directory populated with many long-named files; an ls request then leaves the Telnet server unable to respond, without reported data disclosure or modification.
Summary
What happened
Buffer overflow in the Contiki 3.0 Telnet service allows remote attackers to interrupt the service by listing many long file names. Telnet command handling stores all ls output in a fixed-length response buffer without checking whether each write succeeds, so output is lost after the buffer fills. Exploitation requires a directory populated with many long-named files; an ls request then leaves the Telnet server unable to respond, without reported data disclosure or modification.
The record
- CVE
- CVE-2021-38386
- Published
- Aug 10, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 10, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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
- Long-filename directory reproduction procedureproof 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