full-disclosure - UNIX Tar Security Advisory from TEAM PWN4GE

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <200502030412.j134C7ks005744@turing-police.cc.vt.edu>
From: Valdis.Kletnieks at vt.edu (Valdis.Kletnieks@...edu)
Subject: UNIX Tar Security Advisory from TEAM PWN4GE 

On Wed, 02 Feb 2005 23:18:12 +0100, Volker Tanger said:

> Alternatively the TAR binary might be SUID'ed, which is A Bad Idea(TM),
> too - which are all SUID'ed programs that can write to arbitrary
> locations...

And in the prehistoric dawn of the computer era, about 15 years ago, IBM made
one of the first RISC-based systems, the RT.  One of the operating systems
available for it was AIX 2.2 (a SYSV port, which came out before AIX 1.2 for
the x86 family of PS/2 boxes), which indeed shipped with a setuid /bin/tar.

First time I saw that, I said to myself "Damn, I've been hax0red".  Then I
re-installed tar from the original system media - and promptly wished it had
in fact been a trojaned binary.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 226 bytes
Desc: not available
Url : http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20050202/d9bc46ac/attachment.bin