File Transfer Protocol allows data connection hijacking via PASV mode race condition

Overview

There is a vulnerability in the File Transfer Protocol (FTP) that allows an attacker to hijack FTP data connections when the client connects using passive mode (PASV).

Description

In FTP PASV mode, the client makes a control connection to the FTP server (typically port 21/tcp) and requests a PASV data connection. The server responds by listening for client connections on a specified port number, which is supplied to the client via the control connection. If an attacker can make a connection to the listening port before the client connects, the server will transmit the data to the attacker instead of the client.

To exploit this vulnerability, the attacker must intercept or guess the port number that the server will use, then make its connection attempt before the client establishes a data connection. If the server chooses port numbers using an easily identifiable pattern (such as incrementally), this vulnerability is trivial to exploit.

Note that this vulnerability was first discovered in February 1999, so it is likely that many FTP servers have been patched to address this issue.

---

Impact

Remote intruders can hijack data requested by a legitimate user. It may also be possible to insert data on to an FTP server if the server is acting in a peering (mirroring) relationship with another server.

---

Solution

Apply a patch from your vendor

Please see the vendor section of this document for information on obtaining patches.

---

Reject data connections from hosts that do not match the control connection host

One possible mitigation strategy is to reject data connections that do not originate from the same IP address as the control connection, but this has several problems. First, it makes the server not strictly compliant with RFC 959. Second, it can be defeated by an attacker on the same machine (or network, if spoofed IP addresses are used).

Use randomly selected PASV ports to decrease likelihood of interception

If the server chooses the PASV listening port randomly, it will be difficult or impossible for an attacker to determine the data port. Note that this will not protect against attackers who are able to intercept the FTP control connection because the FTP server must supply the PASV listening port to the client.

---

Vendor Information

2558

Filter by status: All Affected Not Affected Unknown

Filter by content: __ Additional information available

__ Sort by: Status Alphabetical

Expand all

Javascript is disabled. Click here to view vendors.

Cray Inc. __ Affected

Notified: April 29, 2002 Updated: April 30, 2002

Status

Affected

Vendor Statement

The ftp supplied by Cray, Inc. in Unicos and Unicos/mk is vulnerable. Spr 722300 has been opened to track this problem.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

The CERT/CC has no additional comments at this time.

If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%232558 Feedback>).

Hewlett-Packard Company __ Affected

Notified: April 29, 2002 Updated: May 02, 2002

Status

Affected

Vendor Statement

HP is not vulnerable. By default third party transfer is disabled.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

HP reports that this vulnerability was addressed in August 2000.

If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%232558 Feedback>).

Red Hat Inc. __ Affected

Notified: April 29, 2002 Updated: April 30, 2002

Status

Affected

Vendor Statement

Red Hat Linux since version 6.0 is not affected by this issue. Red Hat Linux prior to version 6.0 may be affected if users are still using the default version of wu-ftpd. Affected users are advised to upgrade to a supported release of Red Hat Linux.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

The CERT/CC has no additional comments at this time.

If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%232558 Feedback>).

SGI __ Affected

Notified: April 29, 2002 Updated: March 26, 2003

Status

Affected

Vendor Statement

We have not received a statement from the vendor.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

-----BEGIN PGP SIGNED MESSAGE-----

______________________________________________________________________________ SGI Security Advisory
`Title : Multiple Vulnerabilities and Enhancements in ftpd
Number : 20030304-01-P
Date : March 24, 2003
Reference: CERT CA-1997-27
Reference: CERT VU#2558
Reference: CERT VU#258721
Reference: CVE CVE-1999-0017
Reference: CVE CVE-1999-0097
Reference: CVE CVE-1999-0351
Reference: SecurityFocus BID#396
Reference: SGI BUGS 856093 856168 872855 878791 879133 880067
Fixed in : IRIX 6.5.20
Fixed in : Patches 4966 or 4999

---

- -----------------------

• — Issue Specifics —

---

It has been reported that there are fundamental design issues in the FTP
protocol which exhibit themselves as vulnerabilities in the ftpd daemon.
1) The “Pizza Thief” exploit, a minor security issue involving FTP
connections when the PASV mode is being used.
See the following URLs for additional details:
<http://www.kb.cert.org/vuls/id/2558&gt;
<https://vulners.com/cve/CVE-1999-0351&gt;
<http://www.infowar.com/iwftp/iw_sec/iw_sec_01.txt&gt;
2) The “FTP_PrivilegedPort” exploit, a minor security issue involving FTP
connections when the PORT mode is being used.
See the following URLs for additional details:
<http://www.kbeta.com/attacklist/FTP_PrivilegedPort.htm&gt;
<http://www.cert.org/advisories/CA-1997-27.html&gt;
<https://vulners.com/cve/CVE-1999-0017&gt;
<ftp://patches.sgi.com/support/free/security/advisories/20020305-02-I&gt;
3) The ftp client can potentially execute server-specified code during
download.
See the following URLs for additional details:
<http://www.kb.cert.org/vuls/id/258721&gt;
<http://www.securityfocus.com/bid/396/discussions/&gt;
<https://vulners.com/cve/CVE-1999-0097&gt;
This bulletin and the patches referenced herein also address the following
enhancements and fixes:
4) If the -S switch is used with ftpd, any subsequent flags are ignored.
5) ftpd needs an option to turn banners off
This has been requested by some entities as a “security by obscurity”
enhancement.
6) ftpd filename globbing error.
`

SGI has investigated the issue and recommends the following steps for neutralizing the exposure. It is HIGHLY RECOMMENDED that these measures be implemented on ALL vulnerable SGI systems.
These issues have been corrected with patches and in future releases of IRIX.

`- --------------

• — Impact —

---

The /usr/etc/ftpd binary is installed by default on IRIX 6.5 systems as part
of eoe.sw.base.
To determine the version of IRIX you are running, execute the following
command:
# /bin/uname -R
That will return a result similar to the following:
# 6.5 6.5.16f
The first number (“6.5”) is the release name, the second (“6.5.16f” in this
case) is the extended release name. The extended release name is the
“version” we refer to throughout this document.
`

`- ----------------------------

• — Temporary Workaround —

---

There is no effective workaround available for these problems if ftp server
functionality is needed. If it is not needed, then you can comment it out
of the /etc/inetd.conf file as shown:
Find the lines in /etc/inetd.conf for ftp:
ftp stream tcp nowait root /usr/etc/ftpd ftpd -l
ftp stream tcp6 nowait root /usr/etc/ftpd ftpd -l
Comment them out by putting a “#” character at the beginning of the lines:
#ftp stream tcp nowait root /usr/etc/ftpd ftpd -l
#ftp stream tcp6 nowait root /usr/etc/ftpd ftpd -l
Then issue the command “killall -HUP inetd”.
Note that it will no longer be possible to connect to the ftp server after
this. SGI recommends either upgrading to IRIX 6.5.20 when available, or
installing the appropriate patch from the listing below.
`

`- ----------------

• — Solution —

---

SGI has provided patches for these vulnerabilities. Our recommendation is to
upgrade to IRIX 6.5.20 when available, or install the appropriate patch.
OS Version Vulnerable? Patch # Other Actions

---

IRIX 3.x unknown Note 1
IRIX 4.x unknown Note 1
IRIX 5.x unknown Note 1
IRIX 6.0.x unknown Note 1
IRIX 6.1 unknown Note 1
IRIX 6.2 unknown Note 1
IRIX 6.3 unknown Note 1
IRIX 6.4 unknown Note 1
IRIX 6.5 yes Notes 2 & 3
IRIX 6.5.1 yes Notes 2 & 3
IRIX 6.5.2 yes Notes 2 & 3
IRIX 6.5.3 yes Notes 2 & 3
IRIX 6.5.4 yes Notes 2 & 3
IRIX 6.5.5 yes Notes 2 & 3
IRIX 6.5.6 yes Notes 2 & 3
IRIX 6.5.7 yes Notes 2 & 3
IRIX 6.5.8 yes Notes 2 & 3
IRIX 6.5.9 yes Notes 2 & 3
IRIX 6.5.10 yes Notes 2 & 3
IRIX 6.5.11 yes Notes 2 & 3
IRIX 6.5.12 yes Notes 2 & 3
IRIX 6.5.13 yes Notes 2 & 3
IRIX 6.5.14 yes Notes 2 & 3
IRIX 6.5.15m yes 4999 Note 4
IRIX 6.5.15f yes 4999 Note 4
IRIX 6.5.16m yes 4999 Note 4
IRIX 6.5.16f yes 4999 Note 4
IRIX 6.5.17m yes 4999 Note 4
IRIX 6.5.17f yes 4999 Note 4
IRIX 6.5.18m yes 4999 Note 4
IRIX 6.5.18f yes 4999 Note 4
IRIX 6.5.19m yes 4966 Note 4
IRIX 6.5.19f yes 4966 Note 4
IRIX 6.5.20 no
NOTES
1) This version of the IRIX operating has been retired.
Upgrade to an actively supported IRIX operating system.
See <http://support.sgi.com/&gt; for more information.
2) If you have not received an IRIX 6.5.X CD for IRIX 6.5,
contact your SGI Support Provider or see the URL:
<http://support.sgi.com/&gt;
3) Upgrade to IRIX 6.5.20 when available.
4) Install the patch 4966 or 4999.
##### Patch File Checksums ####
The actual patch will be a tar file containing the following files:
Filename: README.patch.4966
Algorithm #1 (sum -r): 30429 9 README.patch.4966
Algorithm #2 (sum): 5685 9 README.patch.4966
MD5 checksum: 39DDB6631D6C1B480ACC1A3968F26068
Filename: patchSG0004966
Algorithm #1 (sum -r): 42639 2 patchSG0004966
Algorithm #2 (sum): 2056 2 patchSG0004966
MD5 checksum: E687D985CC484946F14F50DBFFBD594C
Filename: patchSG0004966.eoe_man
Algorithm #1 (sum -r): 25807 24 patchSG0004966.eoe_man
Algorithm #2 (sum): 24005 24 patchSG0004966.eoe_man
MD5 checksum: BB6BEE93FBD08DFB9BF54E423F4C8D8B
Filename: patchSG0004966.eoe_sw
Algorithm #1 (sum -r): 11787 243 patchSG0004966.eoe_sw
Algorithm #2 (sum): 20503 243 patchSG0004966.eoe_sw
MD5 checksum: 5274BFF4AE60481CDB2D86E2935AB2EC
Filename: patchSG0004966.idb
Algorithm #1 (sum -r): 20861 2 patchSG0004966.idb
Algorithm #2 (sum): 57507 2 patchSG0004966.idb
MD5 checksum: 72C2E78FC7E0CEAFC9BA1FEEC68A98A7
`

Filename: README.patch.4999 Algorithm #1 (sum -r): 56850 9 README.patch.4999 Algorithm #2 (sum): 16454 9 README.patch.4999 MD5 checksum: E601761F27690973ED6F62DEFC1D3EBD
Filename: patchSG0004999 Algorithm #1 (sum -r): 29824 4 patchSG0004999 Algorithm #2 (sum): 50625 4 patchSG0004999 MD5 checksum: 3161FF9FA27C290151AC0777FCBED5D2
Filename: patchSG0004999.eoe_man Algorithm #1 (sum -r): 63013 23 patchSG0004999.eoe_man Algorithm #2 (sum): 18912 23 patchSG0004999.eoe_man MD5 checksum: 93A9E7416CDFF51C00A904B37716BE14
Filename: patchSG0004999.eoe_sw Algorithm #1 (sum -r): 47031 227 patchSG0004999.eoe_sw Algorithm #2 (sum): 9364 227 patchSG0004999.eoe_sw MD5 checksum: A030266BFE7636F6BE58B29AE4E37338
Filename: patchSG0004999.idb Algorithm #1 (sum -r): 16581 2 patchSG0004999.idb Algorithm #2 (sum): 57620 2 patchSG0004999.idb MD5 checksum: C98A4A3F5550DF0B09CEE17A8C8102A3

`- ------------------------

• — Acknowledgments ----

---

SGI wishes to thank Security Focus, CERT, and the users of the Internet
Community at large for their assistance in this matter.
`

`- -------------

• — Links —

---

SGI Security Advisories can be found at:
<http://www.sgi.com/support/security/&gt; and
<ftp://patches.sgi.com/support/free/security/advisories/&gt;
SGI Security Patches can be found at:
<http://www.sgi.com/support/security/&gt; and
<ftp://patches.sgi.com/support/free/security/patches/&gt;
SGI patches for IRIX can be found at the following patch servers:
<http://support.sgi.com/&gt; and <ftp://patches.sgi.com/&gt;
SGI freeware updates for IRIX can be found at:
<http://freeware.sgi.com/&gt;
SGI fixes for SGI open sourced code can be found on:
<http://oss.sgi.com/projects/&gt;
SGI patches and RPMs for Linux can be found at:
<http://support.sgi.com/&gt; or <http://oss.sgi.com/projects/&gt;
SGI patches for Windows NT or 2000 can be found at:
<http://support.sgi.com/&gt;
IRIX 5.2-6.4 Recommended/Required Patch Sets can be found at:
<http://support.sgi.com/&gt; and <ftp://patches.sgi.com/support/patchset/&gt;
IRIX 6.5 Maintenance Release Streams can be found at:
<http://support.sgi.com/&gt;
IRIX 6.5 Software Update CDs can be obtained from:
<http://support.sgi.com/&gt;
The primary SGI anonymous FTP site for security advisories and patches is
patches.sgi.com (216.32.174.211). Security advisories and patches are
located under the URL <ftp://patches.sgi.com/support/free/security/&gt;
For security and patch management reasons, ftp.sgi.com (mirrors
patches.sgi.com security FTP repository) lags behind and does not do a
real-time update.
`

`- -----------------------------------------

• — SGI Security Information/Contacts —

---

If there are questions about this document, email can be sent to
[email protected].
------oOo------
SGI provides security information and patches for use by the entire SGI
community. This information is freely available to any person needing the
information and is available via anonymous FTP and the Web.
The primary SGI anonymous FTP site for security advisories and patches is
patches.sgi.com (216.32.174.211). Security advisories and patches are
located under the URL <ftp://patches.sgi.com/support/free/security/&gt;
The SGI Security Headquarters Web page is accessible at the URL:
<http://www.sgi.com/support/security/&gt;
For issues with the patches on the FTP sites, email can be sent to
[email protected].
For assistance obtaining or working with security patches, please
contact your SGI support provider.
------oOo------
SGI provides a free security mailing list service called wiretap and
encourages interested parties to self-subscribe to receive (via email) all
SGI Security Advisories when they are released. Subscribing to the mailing
list can be done via the Web
(<http://www.sgi.com/support/security/wiretap.html&gt;) or by sending email to
SGI as outlined below.
% mail [email protected]
subscribe wiretap <YourEmailAddress>
end
^d
In the example above, <YourEmailAddress> is the email address that you wish
the mailing list information sent to. The word end must be on a separate
line to indicate the end of the body of the message. The control-d (^d) is
used to indicate to the mail program that you are finished composing the
mail message.
`

------oOo------
SGI provides a comprehensive customer World Wide Web site. This site is located at <http://www.sgi.com/support/security/> .
------oOo------
If there are general security questions on SGI systems, email can be sent to [email protected].
For reporting *NEW* SGI security issues, email can be sent to [email protected] or contact your SGI support provider. A support contract is not required for submitting a security report.
______________________________________________________________________________ This information is provided freely to all interested parties and may be redistributed provided that it is not altered in any way, SGI is appropriately credited and the document retains and includes its valid PGP signature.
-----BEGIN PGP SIGNATURE----- Version: 2.6.2
iQCVAwUBPn9pLbQ4cFApAP75AQFF1gP/a7ZJjTA3Iilkni127lYj6cu0C+V2vCYE 77xDTherrQU2esS2RAZGmiCAniqSFMCp91MgGvM7+CEd36MctM7APdhgj074TvV0 w0vRpAooDU78y5+E/cEIy6NECtBoJxFSRVZGBBYLATtq2LdXGaLdyiFfOF0NrnDM ZiUdTrT0zXI= =qFQr -----END PGP SIGNATURE-----

If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%232558 Feedback>).

WU-FTPD Development Group __ Affected

Notified: February 15, 1999 Updated: April 30, 2002

Status

Affected

Vendor Statement

We have not received a statement from the vendor.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

This vulnerability was addressed in February 1999 by the WU-FTPD Development Group with the release of WU-FTPD version 2.4.2 Beta 18 VR 14. For more information, please see:

ftp://ftp.wu-ftpd.org/pub/wu-ftpd-attic/ANNOUNCE-2.4.2-beta-18-vr14
In May 1999, the patched code from version 2.4.2 Beta 18 VR 14 was introduced into WU-FTPD 2.5.0, the first official release to include this code. The latest release of WU-FTP can be obtained from:

ftp://ftp.wu-ftpd.org/pub/wu-ftpd/

If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%232558 Feedback>).

Apple Computer Inc. Unknown

Notified: April 29, 2002 Updated: April 29, 2002

Status

Unknown

Vendor Statement

We have not received a statement from the vendor.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

The CERT/CC has no additional comments at this time.

If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%232558 Feedback>).

BSDI Unknown

Notified: April 29, 2002 Updated: April 29, 2002

Status

Unknown

Vendor Statement

We have not received a statement from the vendor.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

The CERT/CC has no additional comments at this time.

If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%232558 Feedback>).

Cisco Systems Inc. Unknown

Notified: April 30, 2002 Updated: May 16, 2002

Status

Unknown

Vendor Statement

We have not received a statement from the vendor.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

The CERT/CC has no additional comments at this time.

If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%232558 Feedback>).

Data General Unknown

Notified: April 29, 2002 Updated: April 29, 2002

Status

Unknown

Vendor Statement

We have not received a statement from the vendor.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

The CERT/CC has no additional comments at this time.

If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%232558 Feedback>).

Debian Unknown

Notified: April 29, 2002 Updated: April 29, 2002

Status

Unknown

Vendor Statement

We have not received a statement from the vendor.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

The CERT/CC has no additional comments at this time.

If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%232558 Feedback>).

F5 Networks Unknown

Notified: April 29, 2002 Updated: April 29, 2002

Status

Unknown

Vendor Statement

We have not received a statement from the vendor.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

The CERT/CC has no additional comments at this time.

If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%232558 Feedback>).

FreeBSD Unknown

Notified: April 29, 2002 Updated: April 29, 2002

Status

Unknown

Vendor Statement

We have not received a statement from the vendor.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

The CERT/CC has no additional comments at this time.

If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%232558 Feedback>).

Fujitsu Unknown

Notified: April 29, 2002 Updated: April 29, 2002

Status

Unknown

Vendor Statement

We have not received a statement from the vendor.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

The CERT/CC has no additional comments at this time.

If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%232558 Feedback>).

Guardian Digital Inc. Unknown

Notified: April 29, 2002 Updated: April 29, 2002

Status

Unknown

Vendor Statement

We have not received a statement from the vendor.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

The CERT/CC has no additional comments at this time.

If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%232558 Feedback>).

IBM Unknown

Notified: April 29, 2002 Updated: April 29, 2002

Status

Unknown

Vendor Statement

We have not received a statement from the vendor.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

The CERT/CC has no additional comments at this time.

If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%232558 Feedback>).

MandrakeSoft Unknown

Notified: April 29, 2002 Updated: April 29, 2002

Status

Unknown

Vendor Statement

We have not received a statement from the vendor.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

The CERT/CC has no additional comments at this time.

If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%232558 Feedback>).

Microsoft Corporation __ Unknown

Notified: April 29, 2002 Updated: July 05, 2002

Status

Unknown

Vendor Statement

Microsoft has found that this issue does not affect IIS 5.0 or greater.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

The CERT/CC has no additional comments at this time.

If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%232558 Feedback>).

NEC Corporation Unknown

Notified: April 29, 2002 Updated: April 29, 2002

Status

Unknown

Vendor Statement

We have not received a statement from the vendor.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

The CERT/CC has no additional comments at this time.

If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%232558 Feedback>).

NcFTP Software Unknown

Notified: April 29, 2002 Updated: April 29, 2002

Status

Unknown

Vendor Statement

We have not received a statement from the vendor.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

The CERT/CC has no additional comments at this time.

If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%232558 Feedback>).

NetBSD Unknown

Notified: April 29, 2002 Updated: April 29, 2002

Status

Unknown

Vendor Statement

We have not received a statement from the vendor.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

The CERT/CC has no additional comments at this time.

If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%232558 Feedback>).

OpenBSD Unknown

Notified: April 29, 2002 Updated: April 29, 2002

Status

Unknown

Vendor Statement

We have not received a statement from the vendor.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

The CERT/CC has no additional comments at this time.

If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%232558 Feedback>).

Sequent Unknown

Notified: April 29, 2002 Updated: April 29, 2002

Status

Unknown

Vendor Statement

We have not received a statement from the vendor.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

The CERT/CC has no additional comments at this time.

If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%232558 Feedback>).

Sony Corporation Unknown

Notified: April 29, 2002 Updated: April 29, 2002

Status

Unknown

Vendor Statement

We have not received a statement from the vendor.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

The CERT/CC has no additional comments at this time.

If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%232558 Feedback>).

SuSE Inc. Unknown

Notified: April 30, 2002 Updated: April 29, 2002

Status

Unknown

Vendor Statement

We have not received a statement from the vendor.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

The CERT/CC has no additional comments at this time.

If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%232558 Feedback>).

Sun Microsystems Inc. Unknown

Notified: April 29, 2002 Updated: April 29, 2002

Status

Unknown

Vendor Statement

We have not received a statement from the vendor.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

The CERT/CC has no additional comments at this time.

If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%232558 Feedback>).

The SCO Group (SCO Linux) Unknown

Notified: April 29, 2002 Updated: April 29, 2002

Status

Unknown

Vendor Statement

We have not received a statement from the vendor.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

The CERT/CC has no additional comments at this time.

If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%232558 Feedback>).

The SCO Group (SCO UnixWare) Unknown

Notified: April 29, 2002 Updated: April 29, 2002

Status

Unknown

Vendor Statement

We have not received a statement from the vendor.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

The CERT/CC has no additional comments at this time.

If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%232558 Feedback>).

Unisys Unknown

Notified: April 29, 2002 Updated: April 29, 2002

Status

Unknown

Vendor Statement

We have not received a statement from the vendor.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

The CERT/CC has no additional comments at this time.

If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%232558 Feedback>).

View all 28 vendors __View less vendors __

CVSS Metrics

Group	Score	Vector
Base
Temporal
Environmental

References

• <ftp://ftp.wu-ftpd.org/pub/wu-ftpd-attic/ANNOUNCE-2.4.2-beta-18-vr14&gt;
• <http://www.cert.org/tech_tips/ftp_port_attacks.html&gt;
• <http://www.ietf.org/rfc/rfc959.txt&gt;
• <http://www.infowar.com/iwftp/iw_sec/iw_sec_01.txt&gt;
• <http://www.securityfocus.com/bid/4895&gt;
• <http://online.securityfocus.com/bid/5461&gt;

Acknowledgements

The CERT/CC thanks Gregory A Lundberg and Jeffrey R. Gerber for their detailed explanations of this vulnerability.

This document was written by Jeffrey P. Lanza and Jed M Pickel.

Other Information

CVE IDs:	CVE-1999-0351
Severity Metric:	13.95 Date Public: