dbcve.org
Ws FtpApplication · Ipswitch

CVE-2007-3823

HIGH · 7.8 CVSS v2.0 Published 2007-07-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/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 Logging Server (Logsrv.exe) in IPSwitch WS_FTP 7.5.29.0 allows remote attackers to cause a denial of service (daemon crash) by sending a crafted packet containing a long string to port 5151/udp.

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 IPSwitch WS_FTP 7.5.29.0 Logging Server (Logsrv.exe) is vulnerable to a remote denial of service attack via UDP port 5151. Attackers can crash the daemon by sending a crafted packet containing an excessively long string, likely triggering a buffer overflow condition.

MitigationSince this is a 2007 vulnerability in an older WS_FTP version, the primary remediation is to upgrade to a current supported version or, if the product is end-of-life, disable or firewall UDP port 5151. Consider network segmentation to limit exposure of the logging server.

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
Ws FtpApplication
Affected:= 7.5.29.0

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
None
Availability
Complete

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

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. Verify WS_FTP version 7.5.29.0 is installed
    Check the installed WS_FTP version through Add/Remove Programs, the program's Help > About dialog, or by locating the main executable and viewing its file properties
    Affected if The installed version is exactly 7.5.29.0
  2. Confirm Logging Server component is present
    Locate Logsrv.exe on the system, typically in the WS_FTP installation directory
    Affected if Logsrv.exe exists and is the version from WS_FTP 7.5.29.0
  3. Check if UDP port 5151 is listening
    Use netstat -an or a port scanner to verify if UDP port 5151 is open and bound to a service
    Affected if UDP port 5151 is open and accepting connections
  4. Verify logging server is running
    Check running processes for Logsrv.exe or check the WS_FTP Logging Server service status
    Affected if The Logsrv.exe process or service is active

The system is affected if WS_FTP 7.5.29.0 is installed with the logging server component running and UDP port 5151 is exposed

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

Since this is a 2007 vulnerability in an older WS_FTP version, the primary remediation is to upgrade to a current supported version or, if the product is end-of-life, disable or firewall UDP port 5151. Consider network segmentation to limit exposure of the logging server.

Fix this in Ws Ftp Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,180
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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