Note: This is an archival copy of Security Sun Alert 200310 as previously published on http://sunsolve.sun.com.|
Latest version of this security advisory is available from http://support.oracle.com as Sun Alert 1000235.1.
Solaris 9 Operating System
Solaris 8 Operating System
Date of Resolved Release
A local unprivileged user with "write" access to a Unix File System (UFS) on which UFS logging is enabled (see also ufs(7fs)) may have the ability to cause a "soft hang" of the Solaris operating system, resulting in a Denial-of-Service (DoS) condition.
This issue can occur in the following releases:
To determine if logging is enabled on a file system(s), the following command can be run (this will return one line per file system that has "logging" in its entry):
$ mount | grep logging / on /dev/dsk/c0t0d0s0 read/write/setuid/devices/intr/largefiles/logging/xattr/onerror=panic/dev=220000 8 on Wed Sep 14 18:50:25 2005 /local on /dev/dsk/c0t0d0s1 read/write/setuid/devices/intr/largefiles/logging/xattr/onerror=panic/dev=220000 9 on Wed Sep 14 18:50:41 2005
In the above example, both "/" and "/local" file systems have logging enabled. If the logging option is not present, the system is not vulnerable to this issue.
Should the described issue occur, the first symptom will be that I/O commands operating on the affected file system will hang. This may include commands such as ls(1).
Note: Verification of an occurrence of this issue may also be obtained through examination of a forced crash dump.
To work around the described issue (if this issue has not yet occurred), temporarily suspend logging on all (UFS) file systems to which local unpriviledged users have write access until patches can be applied. This can be accomplished by either:
A) Replacing the "logging" entry with the "nologging" keyword to entries in the "/etc/vfstab" file where logging has been enabled and then remounting the file system,
B) by running the following command:
# mount -o remount,nologging <mount_point>
(the above setting will only persist until the next reboot).
This issue is addressed in the following releases:
This solution has no attachment