Service crash via miscalculated TFTP response buffer
Published Sep 13, 2021 · Updated Aug 4, 2024
A buffer overflow in atftp through 0.7.4 allows remote attackers to crash the atftpd server with a crafted TFTP read request. In tftpd_file.c, response-buffer sizing fails to account for file data, the OACK header, and multiple negotiated option strings written together. No authentication or user interaction is required; successful exploitation terminates the daemon and interrupts TFTP service.
Summary
What happened
A buffer overflow in atftp through 0.7.4 allows remote attackers to crash the atftpd server with a crafted TFTP read request. In tftpd_file.c, response-buffer sizing fails to account for file data, the OACK header, and multiple negotiated option strings written together. No authentication or user interaction is required; successful exploitation terminates the daemon and interrupts TFTP service.
The record
- CVE
- CVE-2021-41054
- Published
- Sep 13, 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
- Sep 13, 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
- PoClient.sh and TestServ.sh crash 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