<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: FTP Vulnerability in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/ftp-vulnerability/m-p/2972290#M120640</link>
    <description>ftp on 11.11 is WU-FTPD so you've got the code already. 11.0 (with recent patches) also has WU-FTPD. The random sequence number issue came up a couple of years ago and I believe there was a patch to resolve it although there were caveats for compatibility issues (primarily for firewalls and proxy servers). As mentioned, changing from ftp to sftp is the preferred solution although it may not be available for other platforms.</description>
    <pubDate>Wed, 14 May 2003 01:59:28 GMT</pubDate>
    <dc:creator>Bill Hassell</dc:creator>
    <dc:date>2003-05-14T01:59:28Z</dc:date>
    <item>
      <title>FTP Vulnerability</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ftp-vulnerability/m-p/2972285#M120635</link>
      <description>Hello.  A recent security scan came up with the following on one of our HP/UX 11.11 servers.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;The FTP protocol uses a main connection, called a control connection.&lt;BR /&gt;Data connections may be opened in two ways:&lt;BR /&gt;1. active data connection&lt;BR /&gt;The client, before a data transfer starts, sends a PORT command on the control&lt;BR /&gt;connection.&lt;BR /&gt;2. passive data connection&lt;BR /&gt;The client, before a data transfer starts, sends a PASV command to the server. The server answers with the IP address and TCP port it will listen to. The client then opens this data connection to the given endpoint on the FTP&lt;BR /&gt;server.&lt;BR /&gt;In PASV mode, both control and data connections are initiated by the client, which makes this mode easier to set up across firewalls.&lt;BR /&gt;Some FTP servers unfortunately open ports in sequential order. The issue is that an intruder could intercept the answer to the PASV command and open the data connection before the legitimate client can do it. The intruder can then steal information (if the intended FTP command is a 'retrieve') or tamper with data on the server (if the intended FTP command is a 'store').&lt;BR /&gt;Please note that this TC can fail if other PASV commands are issued at the time of the test ( in this case, the port numbers returned by the server will not be sequential anymore ).&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Does anyone know is there a patch for the HP ftp daemon to resolve this or do I need to look at replacing the HP ftpd with wu_ftpd or another ftp program?&lt;BR /&gt;&lt;BR /&gt;TIA,&lt;BR /&gt;&lt;BR /&gt;Sean</description>
      <pubDate>Tue, 13 May 2003 16:57:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ftp-vulnerability/m-p/2972285#M120635</guid>
      <dc:creator>Sean OB_1</dc:creator>
      <dc:date>2003-05-13T16:57:44Z</dc:date>
    </item>
    <item>
      <title>Re: FTP Vulnerability</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ftp-vulnerability/m-p/2972286#M120636</link>
      <description>This is the only patch I found.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www2.itrc.hp.com/service/patch/patchDetail.do?patchid=PHNE_27765&amp;amp;context=hpux:800:11:11" target="_blank"&gt;http://www2.itrc.hp.com/service/patch/patchDetail.do?patchid=PHNE_27765&amp;amp;context=hpux:800:11:11&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;I'm not sure it deals with this issue or not.&lt;BR /&gt;&lt;BR /&gt;I recall reading forum posts that say wu-ftpd is just as good as the other possible candidates.&lt;BR /&gt;&lt;BR /&gt;ftpd's real problem is that password exchange is in clear text which creates intercept possibilitiies.  To avoid that you have to switch to secure shell.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www.software.hp.com/cgi-bin/swdepot_parser.cgi/cgi/displayProductInfo.pl?productNumber=T1471AA" target="_blank"&gt;http://www.software.hp.com/cgi-bin/swdepot_parser.cgi/cgi/displayProductInfo.pl?productNumber=T1471AA&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Tue, 13 May 2003 17:28:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ftp-vulnerability/m-p/2972286#M120636</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2003-05-13T17:28:46Z</dc:date>
    </item>
    <item>
      <title>Re: FTP Vulnerability</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ftp-vulnerability/m-p/2972287#M120637</link>
      <description>Steven,&lt;BR /&gt;&lt;BR /&gt;That was the only patch I found as well, and it's already installed on the machines.&lt;BR /&gt;&lt;BR /&gt;I'd really rather not have to replace FTP on their servers, as that is just another app that we'll have to track and patch separately.&lt;BR /&gt;&lt;BR /&gt;Unfortunately only using SSh isn't an option on these servers because their primary appliation only supports telnet.&lt;BR /&gt;</description>
      <pubDate>Tue, 13 May 2003 18:39:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ftp-vulnerability/m-p/2972287#M120637</guid>
      <dc:creator>Sean OB_1</dc:creator>
      <dc:date>2003-05-13T18:39:33Z</dc:date>
    </item>
    <item>
      <title>Re: FTP Vulnerability</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ftp-vulnerability/m-p/2972288#M120638</link>
      <description>I'm probably confused(usually am), but you can run secure shell and ftpd and telnetd simultaneously.&lt;BR /&gt;&lt;BR /&gt;Just because your primary application requires telnet doesn't mean you can't replace ftpd with sftp running from the sshd daemon.&lt;BR /&gt;&lt;BR /&gt;I'm probably missing a lot, and you know the integration issues better than me.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Tue, 13 May 2003 18:51:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ftp-vulnerability/m-p/2972288#M120638</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2003-05-13T18:51:17Z</dc:date>
    </item>
    <item>
      <title>Re: FTP Vulnerability</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ftp-vulnerability/m-p/2972289#M120639</link>
      <description>This isn't an exact answer to your question, but you can limit ftp to use only designated hosts.  Create the /var/adm/inetd.sec file, and give it an entry like:&lt;BR /&gt;ftp allow 192.168.1.100&lt;BR /&gt;This means that ONLY the host at that address can use ftp.  Its not perfect, but it works pretty well.  You can use *'s as wildcards to get a whole range of addresses.  Then if you DO get hacked, you at least know where to start looking for the culprit!&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Chris</description>
      <pubDate>Tue, 13 May 2003 19:00:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ftp-vulnerability/m-p/2972289#M120639</guid>
      <dc:creator>Chris Vail</dc:creator>
      <dc:date>2003-05-13T19:00:21Z</dc:date>
    </item>
    <item>
      <title>Re: FTP Vulnerability</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ftp-vulnerability/m-p/2972290#M120640</link>
      <description>ftp on 11.11 is WU-FTPD so you've got the code already. 11.0 (with recent patches) also has WU-FTPD. The random sequence number issue came up a couple of years ago and I believe there was a patch to resolve it although there were caveats for compatibility issues (primarily for firewalls and proxy servers). As mentioned, changing from ftp to sftp is the preferred solution although it may not be available for other platforms.</description>
      <pubDate>Wed, 14 May 2003 01:59:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ftp-vulnerability/m-p/2972290#M120640</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2003-05-14T01:59:28Z</dc:date>
    </item>
  </channel>
</rss>

