CVE-2024-23985: n/a
Source CVE Database V5
Not known to be exploited · public exploit available (Metasploit) · CVSS 7.5 High.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 3.5% chance of exploitation in 30 days – higher than 89% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 25 Jan 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| n/a n/a | Affected
| Fixed in– |
AI-suggested
To mitigate this vulnerability, organizations should first verify if they are running EzServer 6.4.017 or any affected versions. Deploying intrusion detection/prevention systems (IDS/IPS) with signatures or anomaly detection for unusually long RNTO commands can help block exploit attempts. Network segmentation to isolate FTP servers from critical infrastructure reduces potential impact. Administrators should also consider disabling or limiting FTP services if not essential or migrating to more secure file transfer protocols (e.g., SFTP or FTPS) that provide better security controls. Monitoring server logs for abnormal command lengths and crashes can provide early warning signs. Once a vendor patch or update is released, prompt application is critical. Additionally, maintaining regular backups and having incident response plans for DoS scenarios will improve resilience.
Description
EzServer 6.4.017 allows a denial of service (daemon crash) via a long string, such as one for the RNTO command.