dbcve.org
FtpdApplication · Netbsd

CVE-2002-2245

MEDIUM · 5.0 CVSS v2.0 Published 2002-12-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
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
ftpd in NetBSD 1.5 through 1.5.3 and 1.6 does not properly quote a digit in response to a STAT command for a filename that contains a carriage return followed by a digit, which can cause firewalls and other intermediary devices to lose proper track of the FTP session.

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

The ftpd in NetBSD 1.5-1.5.3 and 1.6 fails to properly quote digits in STAT command responses when filenames contain a carriage return followed by a digit. This causes improper parsing by firewalls and intermediary devices, potentially causing them to lose track of FTP session boundaries.

MitigationUpgrade to a patched NetBSD version or apply the vendor security patch. For legacy systems, consider network-level filtering to sanitize FTP responses or restrict FTP access through problematic intermediaries.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FtpdApplication
Affected:= 1.5= 1.5.1= 1.5.2= 1.5.3= 1.6

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
Authentication
None
Confidentiality
None
Integrity
Partial
Availability
None

AV:N/AC:L/Au:N/C:N/I:P/A:N

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 NetBSD version
    Run 'uname -r' or check /etc/os-release to determine the installed NetBSD version
    Affected if Version is 1.5, 1.5.1, 1.5.2, 1.5.3, or 1.6
  2. Verify ftpd is installed
    Check for the ftpd binary at /usr/libexec/ftpd or run 'which ftpd'
    Affected if ftpd binary exists on the system
  3. Confirm ftpd service status
    Check if ftpd is running or enabled by examining running processes ('ps aux | grep ftpd') or system service configuration
    Affected if ftpd is currently running or configured to start
  4. Check FTP service accessibility
    Verify port 21 is listening for FTP connections using 'netstat -an | grep :21' or 'sockstat | grep ftp'
    Affected if FTP service is accessible on the network

You are affected if you are running NetBSD 1.5 through 1.6 with ftpd enabled and accessible, as the vulnerability exists specifically in these NetBSD ftpd versions.

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

Upgrade to a patched NetBSD version or apply the vendor security patch. For legacy systems, consider network-level filtering to sanitize FTP responses or restrict FTP access through problematic intermediaries.

Fix this in Ftpd Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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