full-disclosure - Possible race condition in Symantec AntiVirus Scan Engine for Red Hat Linux during LiveUpdate

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] [day] [month] [year] [list]

Message-ID: <200402161621.i1GGLdec009058@turing-police.cc.vt.edu>
From: Valdis.Kletnieks at vt.edu (Valdis.Kletnieks@...edu)
Subject: Possible race condition in Symantec AntiVirus Scan Engine for Red Hat Linux during LiveUpdate 

On Mon, 16 Feb 2004 16:49:53 +0100, "Dr. Peter Bieringer" said:

> logfile=/tmp/LiveUpdate.log  <---!!!!!!
> 
> Impact:
> Before first run of LiveUpdate (like suggested in doc, user "symantec" does 
> this) a possible race condition via a symlink attack by another user will 
> result in the creation of a new file (as user "symantec") or appending 
> LiveUpdate log to an existent file (owned by user "symantec").

For bonus points, figure out what happens if you reboot and your /etc/fstab has this:

none                    /tmp            tmpfs   mode=1777       0 0

The gift that keeps on giving. ;)
-------------- 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/20040216/4c7ba957/attachment.bin