MacOS X 10.10 and FreeBSD 10 Ftp Remote Comand Execution

Re:MacOS X 10.10 and FreeBSD 10 Ftp Remote Comand Execution by fyolnish on Tuesday October 28, 2014 @10:11PM (#8525116)

What possible reason could the authors have had to pass everything following a pipe into popen? Did they think they were writing a shell?

[ Parent | on HN ]

Re:MacOS X 10.10 and FreeBSD 10 Ftp Remote Comand Execution by kps on Tuesday October 28, 2014 @11:31PM (#8525380)

When you're using ftp interactively, at the 'ftp>' prompt, you can optionally supply a local file name to the 'get' command,

  get remote-file [local-file]

and that local-file can begin with a '|' to indicate that you want the remote file piped to a command, e.g.

  get README |less

Apparently this handling of the interactive local file name was mistakenly applied to local files names derived from remote file names after an HTTP redirect from the command line.

(Incidentally the interactive modes of ftp and telnet, with their 'command>' prompts, are the last vestiges in unix of TENEX on the ARPANET.)

[ Parent | on HN ]

Re:MacOS X 10.10 and FreeBSD 10 Ftp Remote Comand Execution by tlrobinson on Wednesday October 29, 2014 @12:03AM (#8525467)

Very reminiscent of Shellshock, actually. Never treat data as code unless very explicitly told to.

[ Parent | on HN ]

Re:MacOS X 10.10 and FreeBSD 10 Ftp Remote Comand Execution by ams6110 on Wednesday October 29, 2014 @09:46AM (#8527098)

Interactive ftp is a shell, for file transfer operations.

[ Parent | on HN ]