Bug 6232

Summary: Security issue with autofs
Product: [Retired] Red Hat Linux Reporter: ggm
Component: autofsAssignee: Cristian Gafton <gafton>
Status: CLOSED RAWHIDE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 6.1Keywords: Security
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2000-02-02 14:23:20 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description ggm 1999-10-22 10:32:17 UTC
I was having a play around with autofs.  The default
installation provides a mount point of /misc/cd which will
mount /dev/cdrom.

Say, for instance, I have a suid root bash shell burned onto
a CD.  I can gain root access.  That easy.

The solution would be to distribute the default
/etc/auto.misc to have the cd mount point with the
parameters -fstype=iso9660,nosuid,nodev,noexec to be safer.

Comment 1 Nalin Dahyabhai 2000-02-02 14:23:59 UTC
The nosuid and nodev flags will be added to the defaults for autofs-3.1.4-2 and
later.

I don't believe adding noexec would make anything safer, and it would certainly
annoy anyone trying to install software from a disc with an installer on the CD
itself (lots of unhappy Quake III players, not a pretty thought).  But I'm not a
security expert.  If you know of any holes that remain open by not adding
noexec, please reopen this bug and I'll take a closer look.