Service crash via oversized virtual path mapping
Published Dec 17, 2021 · Updated Aug 4, 2024
Buffer overflow in FTPShell Server 6.83 allows attackers to crash the service through oversized Virtual Path Mapping input. The public proof of concept enters 417 characters in the mapping field and demonstrates a crash, while the exact unchecked memory-copy operation is undisclosed. The published trigger requires local access to the account-configuration interface; public records do not establish a remote delivery path.
Summary
What happened
Buffer overflow in FTPShell Server 6.83 allows attackers to crash the service through oversized Virtual Path Mapping input. The public proof of concept enters 417 characters in the mapping field and demonstrates a crash, while the exact unchecked memory-copy operation is undisclosed. The published trigger requires local access to the account-configuration interface; public records do not establish a remote delivery path.
The record
- CVE
- CVE-2020-18077
- Published
- Dec 17, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120, T1499.004
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Dec 17, 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
- FTPShell Server 6.83 denial-of-service proof of conceptproof 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