Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
ReconConnect anonymously to LightFTP TCP/21
-
DeliveryIssue LIST to open data connection and spawn worker thread
-
ExploitRapidly send ABOR to trigger control thread close
-
InstallRace control thread descriptor close against worker_thread_cleanup
-
C2OS reassigns stale file descriptor to unrelated resource
-
ExecuteWorker thread operates on wrong resource
-
ImpactFTP server crashes (denial of service)
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Missing synchronization
|
| Exploitation Conditions | Anonymous FTP access must be enabled on the LightFTP instance - this is the primary enabling condition, as the LIST/ABOR sequence can be issued without any credentials when anonymous login is permitted. The CVSS PR:N metric confirms no authentication is required. Exploitation further requires network-level reachability to TCP port 21 (or the configured FTP control port). The race condition is timing-dependent: the attacker must issue ABOR with sufficient proximity to the LIST-initiated data transfer to interleave with worker_thread_cleanup execution; this is reflected in AC:H and means unreliable, probabilistic triggering rather than guaranteed single-attempt success. What limits exploitation: (1) race window timing reduces single-attempt reliability (AC:H); (2) impact is confined to availability - no credential theft or code execution path identified; (3) anonymous access being disabled would entirely prevent unauthenticated exploitation. There is no requirement for a specific platform, OS, or non-default compile option beyond running LightFTP through 2.4 with anonymous FTP enabled. |
| Impact | The CVSS 4.0 vector AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N scores 8.2 and signals a network-reachable, unauthenticated attack with high availability impact but no confidentiality or integrity consequences. The AC:H rating honestly reflects the timing dependency inherent in triggering a race condition - exploitation requires repeated attempts and favorable scheduling, not a trivial single-packet trigger. A publicly available PoC (GitHub issue #75, tagged 'exploit' by cveorg) lowers the bar for opportunistic attackers who can automate the timing. However, LightFTP has a niche deployment footprint, limiting aggregate exposure. No EPSS score was provided in the input data, so exploitation probability cannot be quantitatively compared. The absence of CISA KEV listing suggests active mass exploitation has not been observed. Overall: moderate operational priority - high for any organization knowingly running LightFTP with anonymous access enabled on a network-exposed port, low for most enterprises that do not deploy this software. |
| Exploit ScenarioDerived | An attacker connects anonymously to a LightFTP instance exposed on TCP port 21, issues a LIST command to open a data connection and trigger the worker thread, then rapidly sends ABOR in a tight loop to race the control thread's descriptor close against the worker thread's concurrent use. When timing aligns, the OS closes and reassigns the stale file descriptor to an unrelated resource mid-operation, causing undefined behavior that crashes the server. A publicly available PoC on GitHub (issue #75) demonstrates this sequence, making automated, repeated exploitation straightforward despite the AC:H complexity rating. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 06, 2026
Unauthenticated remote denial of service in LightFTP through version 2.4 exploits multiple data race conditions in ftpserv.c via the LIST/ABOR command sequence. The control thread closes shared data_socket and file_fd descriptors while worker threads concurrently reference the same fields in worker_thread_cleanup, enabling the OS to reassign stale descriptors to unrelated resources and producing undefined behavior. A publicly available proof-of-concept exists (GitHub issue #75); exploitation has not been confirmed in the wild (not in CISA KEV), but the unauthenticated attack surface and CVSS 4.0 score of 8.2 elevate urgency for exposed deployments.
RemediationAI
No patched release version is identified in the available input data; the upstream fix status is unconfirmed - the GitHub issue at https://github.com/hfiref0x/LightFTP/issues/75 documents the race but no tagged patched release is referenced. Operators should monitor the LightFTP repository for a fix and upgrade immediately upon release. As compensating controls: disable anonymous FTP access entirely if it is not operationally required, since the attack requires no credentials and anonymous access is the primary enabling condition; restrict FTP port access (default TCP 21) at the network perimeter to known trusted source IPs using firewall ACLs, accepting the trade-off of reduced public FTP accessibility; or migrate to an actively maintained FTP server with synchronization primitives protecting shared file descriptor state. These controls do not eliminate the underlying race condition but meaningfully reduce the exposed attack surface until a patch is available.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
LightFTP (hfiref0x/LightFTP) is a compact, open-source FTP server whose protocol handling logic resides in ftpserv.c. The vulnerability class is CWE-820 (Missing Synchronization): the server spawns a control thread and separate worker threads that share mutable state - specifically data_socket and file_fd file descriptor fields - without adequate locking or memory-ordering guarantees. When a client issues LIST to initiate a data transfer and then ABOR to abort it, the control thread races with worker_thread_cleanup, each operating on those shared descriptors concurrently. Because the OS may immediately reassign a closed file descriptor number to a new resource (e.g., an unrelated socket or file), the worker thread subsequently performs I/O on the wrong resource, leading to undefined behavior and server crash. The CPE cpe:2.3:a:hfiref0x:lightftp:*:*:*:*:*:*:*:* covers all tracked versions through 2.4. This is a classic TOCTOU-adjacent descriptor-reuse race, made exploitable remotely because anonymous FTP sessions can trigger the LIST/ABOR sequence without credentials.
Know when Lightftp gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
Network-reachable anonymous attack (AV:N, PR:N) but race condition requires timing precision (AC:H); impact is availability-only crash with no confidentiality or integrity loss (C:N/I:N/A:H, S:U).
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
DescriptionCVE.org
LightFTP through 2.4 contains multiple data race vulnerabilities in ftpserv.c that allow anonymous attackers to cause undefined behavior by issuing LIST followed by ABOR commands without authentication. The control thread closes data_socket and file_fd descriptors while worker threads concurrently operate on the same fields in worker_thread_cleanup, allowing stale file descriptors to be reassigned by the OS and subsequently used by worker threads on unrelated resources, resulting in potential denial of service.
Latest POC
1 PoC candidate from github (unverified)
Sign in to open the public PoC links collected for this CVE.
Executive ViewAI
LightFTP versions through 2.4 are vulnerable to unauthenticated remote denial of service attacks triggered by specific FTP command sequences. Organizations operating LightFTP on internet-facing systems face immediate risk of service disruption, with no patch currently available from the vendor. This exposure directly impacts operational availability and business continuity for any dependent workflows.
No vendor-released patch identified at time of analysis. Interim mitigations: (1) Restrict network access to FTP ports from trusted sources only via firewall rules; (2) Implement aggressive connection rate limiting and per-IP connection throttling on port 21; (3) Deploy process monitoring to detect and auto-restart ftpserv on crash; (4) Block or rate-limit LIST and ABOR command sequences via proxy or WAF if possible; (5) Disable ABOR command at application level if operationally feasible; (6) Prepare contingency deployment of vetted alternative FTP server software.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
LightFTP version 1.1 is vulnerable to a buffer overflow in the "writelogentry" function resulting a denial of services o
A race condition in LightFTP through 2.2 allows an attacker to achieve path traversal via a malformed FTP request. Rated
A buffer overflow in the g_cfg.MaxUsers component of LightFTP v2.0 allows attackers to cause a Denial of Service (DoS) v
EUVD-2026-53933
GHSA-6269-2q48-xxqm
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB