dbcve.org
Race ConditionWeakness · CWE-362

CVE-2024-11144

HIGH · 7.5 CVSS v3.1 Published 2024-12-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The server lacks thread safety and can be crashed by anomalous data sent by an anonymous user from a remote network. The crash causes the FTP service to become unavailable, affecting all users and processes that rely on it for file transfers. If the crash occurs during file upload or download, it could lead to incomplete file transfers, potentially corrupting data. The repeated crash might also affect the stability of the underlying system, especially if it leads to resource leaks or affects other services.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The FTP server has a thread safety vulnerability where anomalous data from a remote anonymous user can trigger a crash. The lack of proper synchronization in handling concurrent connections allows a single malicious request to corrupt shared state and cause the service to become unavailable, potentially corrupting in-flight file transfers.

MitigationImplement thread-safe handling of concurrent FTP connections using proper synchronization primitives (mutexes/locks) for all shared state, and add input validation to reject anomalous data before processing.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if an FTP server is running
    Check for listening FTP services: on Linux run 'netstat -tlnp | grep :21' or 'ss -tlnp | grep :21'; on Windows run 'netstat -an | findstr :21' or check services named FTP
    Affected if An FTP server daemon is listening on port 21 or configured FTP service is active
  2. Confirm anonymous FTP access is enabled
    Check FTP server configuration files (e.g., vsftpd.conf, proftpd.conf, IIS FTP settings, or /etc/ftpusers) for 'anonymous_enable=YES' or anonymous access settings; attempt connection with user 'anonymous'
    Affected if Anonymous logins are permitted on the FTP server
  3. Verify concurrent connection handling is in use
    Review FTP server configuration for connection pooling, max instances, or concurrent session limits; check if multiple clients can connect simultaneously
    Affected if The FTP server allows multiple simultaneous connections from any source
  4. Check installed FTP server version
    Query the FTP server binary or package: run 'vsftpd -v', 'proftpd -v', 'twisted -v' (for Twistd), or check installed package via 'dpkg -l | grep ftp' or 'rpm -qa | grep ftp'; for Windows IIS FTP, check via inetmgr or registry
    Affected if The installed version matches or falls within affected version ranges if known; if version is unknown, assume potential exposure when other conditions are met
  5. Inspect for thread-safety or synchronization configurations
    Review FTP server logs and configuration for mutex, lock, or thread-safety related settings; check system logs (/var/log/ftp.log, /var/log/syslog) for crash indicators or race condition warnings
    Affected if Configuration lacks thread-safety primitives OR crash/error logs indicate instability under concurrent load
  6. Test for anomalous data handling
    If safe to do in isolated environment, send malformed FTP commands (e.g., invalid format, overflow input) from multiple concurrent sessions while monitoring service responsiveness
    Affected if Service becomes unresponsive, crashes, or exhibits unexpected behavior when processing concurrent anomalous requests

The environment is affected if an FTP server with anonymous access enabled is running and handling concurrent connections, especially if the version is unpatched or unknown, as the lack of proper synchronization allows a single malicious anonymous request to corrupt shared state and crash the service.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement thread-safe handling of concurrent FTP connections using proper synchronization primitives (mutexes/locks) for all shared state, and add input validation to reject anomalous data before processing.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-11144 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-11144 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data