Opened 18 years ago
Last modified 18 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)
Change History (2)
by , 18 years ago
Attachment: | filezilla.txt added |
---|
comment:1 by , 18 years ago
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.
Filezilla_dump