dbcve.org
Integer OverflowWeakness · CWE-190

CVE-2025-14242

MEDIUM · 6.5 CVSS v3.1 Published 2026-01-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
A flaw was found in vsftpd. This vulnerability allows a denial of service (DoS) via an integer overflow in the ls command parameter parsing, triggered by a remote, authenticated attacker sending a crafted STAT command with a specific byte sequence.

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 · moderate confidence

Integer overflow vulnerability in vsftpd's ls command parameter parsing allows a remote, authenticated attacker to cause denial of service via a crafted STAT command containing a specific byte sequence.

MitigationApply vendor patches for vsftpd when available; until then, restrict FTP access to trusted authenticated users only to reduce attack surface.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 vsftpd installation and version
    Run 'vsftpd -v' or check package manager (dpkg -l | grep vsftpd, rpm -qa | grep vsftpd) to retrieve the installed version number
    Affected if Version falls within the affected range and has not been patched
  2. Confirm vsftpd service is running
    Check if the vsftpd process is active: 'ps aux | grep vsftpd' or 'systemctl status vsftpd'
    Affected if Service is running and exposed to network
  3. Verify FTP access is enabled for remote users
    Review vsftpd configuration file (typically /etc/vsftpd.conf or /etc/vsftpd/vsftpd.conf) for 'anonymous_enable=YES' or 'local_enable=YES' settings, and check firewall rules for port 21
    Affected if Remote authenticated access is permitted (local_enable=YES) or anonymous access is allowed (anonymous_enable=YES)
  4. Confirm network exposure
    Check if FTP port 21 is listening on external interfaces: 'netstat -tlnp | grep :21' or 'ss -tlnp | grep :21'
    Affected if Service is bound to non-localhost addresses and accessible from network

Environment is affected if vsftpd is running with a vulnerable version and accepts remote authenticated or anonymous FTP connections that can issue the STAT command.

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

Apply vendor patches for vsftpd when available; until then, restrict FTP access to trusted authenticated users only to reduce attack surface.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-14242 — 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-2025-14242 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