Date: Mon, 28 Oct 1996 02:10:33 -0500 (EST) From: mi@aldan.ziplink.net To: FreeBSD-gnats-submit@freebsd.org Subject: misc/1910: filenames with unusual characters and /etc/security (or find(1)) Message-ID: <199610280710.CAA07105@rtfm.ziplink.net> Resent-Message-ID: <199610280720.XAA07578@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 1910 >Category: misc >Synopsis: filenames with unusual characters break /etc/security (or find(1)) >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Oct 27 23:20:01 PST 1996 >Last-Modified: >Originator: Mikhail Teterin >Organization: >Release: 2.1.5-RELEASE >Environment: >Description: Date: Sat, 19 Oct 1996 02:00:11 -0400 (EDT) From: Charlie Root <root> Subject: aldan security check output checking setuid files and devices: find: /root/Mail/sent mail: illegal path find: /root/Mail/sent mail/1: illegal path find: /root/Mail/sent mail/.1.summary: illegal path find: /root/Mail/sent mail/2: illegal path find: /root/News/vulisa : illegal path checking for uids of 0: root 0 toor 0 >How-To-Repeat: Make a file with <<space>> in in its name, and see what happens. >Fix: Ignore this part of /etc/security output ;) The potential threat is, one of THIS files may, actually, be setuid... Closer examination, allows to think find(1) is broken on this: find -X /root -type f \( -perm -u+x -or -perm -g+x -or -perm \ -o+x \) \( -perm -u+s -or -perm -g+s \) leads to: find: /root/Mail/sent mail: illegal path find: /root/Mail/sent mail/1: illegal path find: /root/Mail/sent mail/.1.summary: illegal path find: /root/Mail/sent mail/2: illegal path find: /root/News/vulisa : illegal path but I am not sure. >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199610280710.CAA07105>