Bug 6232 - Security issue with autofs
Security issue with autofs
Status: CLOSED RAWHIDE
Product: Red Hat Linux
Classification: Retired
Component: autofs (Show other bugs)
6.1
All Linux
medium Severity medium
: ---
: ---
Assigned To: Cristian Gafton
: Security
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-10-22 06:32 EDT by ggm
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-02-02 09:23:20 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description ggm 1999-10-22 06:32:17 EDT
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 09:23:59 EST
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.

Note You need to log in before you can comment on or make changes to this bug.