Nmap Security Scanner
*Intro
*Ref Guide
*Install Guide
*Download
*Changelog
*Book
*Docs
Security Lists
*Nmap Hackers
*Nmap Dev
*Bugtraq
*Full Disclosure
*Pen Test
*Basics
*More
Security Tools
*Pass crackers
*Sniffers
*Vuln Scanners
*Web scanners
*Wireless
*Exploitation
*Packet crafters
*More
Site News
Site Search:
Exploit World
Advertising
About/Contact
Credits
Sponsors:




bugtraq logo Bugtraq mailing list archives

rcp file transfer hole (was: scp file transfer hole)
From: Markus Friedl <Markus.Friedl () INFORMATIK UNI-ERLANGEN DE>
Date: Mon, 2 Oct 2000 13:06:58 +0200

On Sat, Sep 30, 2000 at 09:21:17PM +0200, Michal Zalewski wrote:
This issue appears quite often - tar suffers from problem of this kind as
well (using cute symlink tricks, you can create an archive, which, when
unpacked, can overwrite or create specific files anywhere in your
filesystem). This time, similar scp vulnerability has been found and
acknowledged in sshd 1.2.xx releases (no information on 2.0.xx).

well, this is not a scp problem.  it's a rcp problem.  scp is nothing
but the plain old rcp protocol over ssh instead of rsh, in the same
way you can do 'cvs' or 'rsync' over ssh.

so all secure-shell's derived from the original ssh-1.2.x releases
suffer from this problem (including openssh). however, ssh-2.x uses a
different protocol and is not vulnerable to this specific bug.

how should this be fixed in a reasonable way?  i don't think questions
similar to "do you really want to create /bla/bla/bla? (yes/no)" would
be useful.

-markus


  By Date           By Thread  

Current thread:
[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]