B
Bennett Haselton
I installed Windows 2000 Server and I'm 99% sure I haven't changed the
default permissions on the NTFS C:\ root directory since then -- but
when I view its Security properties, it lists "Full Control" for
"Everyone".
Is this the default? How can this be secure? Even though those
permissions (of course) do not propagate down to all the
subdirectories on the C:\ drive, that still leaves any user free to
put anything they want in the C:\ drive, and to modify the config.sys
and autoexec.bat files, which inherit their permissions from their
parent by default. (I'm sure those files aren't used much in Windows
2000 Server programs, but there must be something dangerous that an
unprivileged user could do, using them to set environment variables or
something, which would be in effect next time an administrator logged
in? For example, as the unprivileged user "bennett", I could add a
line to autoexec.bat adding the c:\bennett\ directory to the beginning
of %PATH%. Then when an admin logged in, opened a command prompt, and
typed some common command, the version that I put in my directory
could execute, instead of the real one.)
I can only find one page on Google mentioning this as a possibly
security risk, and recommending that administrators change it:
http://www.inetsecurity.info/modules.php?op=modload&name=News&file=article&sid=15
Surely it's a bigger security hole than that? Or am I missing
something?
-Bennett
default permissions on the NTFS C:\ root directory since then -- but
when I view its Security properties, it lists "Full Control" for
"Everyone".
Is this the default? How can this be secure? Even though those
permissions (of course) do not propagate down to all the
subdirectories on the C:\ drive, that still leaves any user free to
put anything they want in the C:\ drive, and to modify the config.sys
and autoexec.bat files, which inherit their permissions from their
parent by default. (I'm sure those files aren't used much in Windows
2000 Server programs, but there must be something dangerous that an
unprivileged user could do, using them to set environment variables or
something, which would be in effect next time an administrator logged
in? For example, as the unprivileged user "bennett", I could add a
line to autoexec.bat adding the c:\bennett\ directory to the beginning
of %PATH%. Then when an admin logged in, opened a command prompt, and
typed some common command, the version that I put in my directory
could execute, instead of the real one.)
I can only find one page on Google mentioning this as a possibly
security risk, and recommending that administrators change it:
http://www.inetsecurity.info/modules.php?op=modload&name=News&file=article&sid=15
Surely it's a bigger security hole than that? Or am I missing
something?
-Bennett