CVE-1999-0219: Rhinosoft Serv-U buffer overflow in CWD and LS commands

CVE-1999-0219 · Severity: high · CVSS 7.8 · Published 1997-07-01

Serv-U is a popular FTP server used to share files over a network. A vulnerability in version 2.5 allows an attacker to remotely crash the server by sending specially crafted commands. This results in a denial of service, preventing legitimate users from accessing or transferring files until the service is manually restarted.

Quick answers

Is CVE-1999-0219 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-1999-0219 being exploited in the wild.
How severe is CVE-1999-0219?
High severity, with a CVSS score of 7.8, published 1 July 1997.
Which products and versions are affected?
Rhinosoft (formerly Cat Soft) Serv-U 2.5 and earlier.
Is there a fix for CVE-1999-0219?
A patch was published on 1999-05-04: Vendor released beta fix following public disclosure Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-1999-0219 attacked?
It is attacked over the network, in a network appliance.
Am I affected by CVE-1999-0219?
Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A buffer overflow vulnerability exists in Serv-U FTP server version 2.5 and potentially earlier versions. The flaw is triggered when the server processes FTP commands that take arguments, such as CWD (Change Working Directory) or LS (List), containing strings of 155 characters or more. An authenticated remote attacker can exploit this by sending a long argument to these commands, leading to a service crash (Denial of Service). The vendor released a beta patch shortly after disclosure to address the boundary checking issue.

Affected products

  • Rhinosoft (formerly Cat Soft) Serv-U 2.5 and earlier

Timeline

  • 1997-07-01: disclosed: Initial vulnerability disclosure date
  • 1999-05-03: other: Public report on NTBUGTRAQ mailing list
  • 1999-05-04: patched: Vendor released beta fix following public disclosure

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.