full-disclosure - Symlink attack techniques

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20051216004424.GA3220@sentinelchicken.org>
Date: Fri Dec 16 00:44:33 2005
From: tim-security at sentinelchicken.org (Tim)
Subject: Symlink attack techniques

> Ok I should have been more precise in my previous mail. In this scenario I 
> don't have control over the output generated by the find command. So 
> basically the cronjob is something like:
> 
> 15 4 ?* * 6 ?root ?/usr/bin/find /home/userA -type f -print > /tmp/report.txt
> 
> Consequently as userB I have no way of influencing what information is printed 
> by the find command to /tmp/report.txt but I can surely 
> control /tmp/report.txt. Any other ideas of how to exploit this to gain root 
> access?

hmmmm, as userB, you do have a way to influence userA's files.  It's
staring you right in the face.

Symlink /tmp/report to a malicious filename under /home/userA, much like
H D Moore suggested.

Then, before the next cronjob runs, re-symlink it to a script that will
execute your command.

Never tried something like that, but with enough hackery, it seems like
it could work.

good luck,
tim