Daemon crash via oversized TFTP RRQ filename
Published Nov 29, 2021 · Updated Aug 4, 2024
Buffer overflow in the Vercot Serva 4.4.0 TFTP server allows remote attackers to crash the daemon via a crafted read request. Serva's RRQ handling accepts a 257-byte filename before the netascii mode field, causing the oversized field to overrun a fixed buffer. An unauthenticated UDP client with access to the TFTP service can interrupt file transfers; the public artifact demonstrates a crash, not code execution.
Summary
What happened
Buffer overflow in the Vercot Serva 4.4.0 TFTP server allows remote attackers to crash the daemon via a crafted read request. Serva's RRQ handling accepts a 257-byte filename before the netascii mode field, causing the oversized field to overrun a fixed buffer. An unauthenticated UDP client with access to the TFTP service can interrupt file transfers; the public artifact demonstrates a crash, not code execution.
The record
- CVE
- CVE-2021-44429
- Published
- Nov 29, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 29, 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
- Serva 4.4.0 TFTP Remote Buffer Overflow Metasploit modulefunctional · 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