Opened 13 years ago

Last modified 13 years ago

#1263 closed Bug report

Port COMMAND IP Parsing

Reported by: matrix-ntn Owned by:
Priority: normal Component: FileZilla Server
Keywords: Cc: matrix-ntn, Tim Kosse
Component version: Operating system type:
Operating system version:

Description

Re,

When a Client (IP 172.17.6.201) connect to Filezilla and send the command:
"PORT 172,017,006,201,11,94"
Then Filzilla Server trys to connect to
172.15.6.201.

I have here a TCP Dump (dumped with wireshark).
I attached the dump (exported as txt)

There you can see, the Request:
PORT 172,017,006,201,57,232
and then trys filezilla
172.17.6.50 172.15.6.201 TCP 20 > 14824 [SYN] Seq=0 Len=0 MSS=1460

That is a bug.

Attachments (1)

filezilla.txt (3.3 KB) - added by matrix-ntn 13 years ago.
Filezilla_dump

Download all attachments as: .zip

Change History (2)

Changed 13 years ago by matrix-ntn

Attachment: filezilla.txt added

Filezilla_dump

comment:1 Changed 13 years ago by Tim Kosse

Client is broken, the numbers in the PORT command aren't supposed to be prefixed by zeros.

Note: See TracTickets for help on using tickets.