Service crash via mishandled file-read error
Published Jan 10, 2020 · Updated Aug 4, 2024
Heap corruption in Bftpd before 5.4 allows remote attackers to trigger a one-byte overwrite when a file-transfer read fails. The command_retr loop treats read() returning -1 as true, then writes a NUL byte to buffer[-1] instead of stopping on the error. The trigger requires a failed read during file download; the demonstrated consequence is a server crash or one-byte heap corruption.
Summary
What happened
Heap corruption in Bftpd before 5.4 allows remote attackers to trigger a one-byte overwrite when a file-transfer read fails. The command_retr loop treats read() returning -1 as true, then writes a NUL byte to buffer[-1] instead of stopping on the error. The trigger requires a failed read during file download; the demonstrated consequence is a server crash or one-byte heap corruption.
The record
- CVE
- CVE-2020-6835
- Published
- Jan 10, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-193, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 10, 2020CVE 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.
Public exploit references
No public exploit references are available in this record.
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