Note: This is an archival copy of Security Sun Alert 200184 as previously published on http://sunsolve.sun.com.|
Latest version of this security advisory is available from http://support.oracle.com as Sun Alert 1000138.1.
Date of Workaround Release
Date of Resolved Release
On Sun systems which use a shared Sun StorEdge QFS file system (see below for details)
On Sun systems which use a shared Sun StorEdge QFS file system (as included in the Sun StorEdge Performance Suite) or a Sun StorEdge SAM-QFS file system (as included in the Sun StorEdge Utilization Suite) local unprivileged users may be able to view the contents of deleted files inside sparse files. The deleted files may contain sensitive information which would not be normally accessible to unprivileged users.
Note: This issue affects Sun QFS and SAM-FS shared file systems only. For more information on sparse files, see InfoDoc 77183.
2. Contributing Factors
This issue can occur in the following releases:
This issue only occurs when a sparse file is written directly on a shared QFS client or written on an NFS client which has mounted a shared QFS filesystem from a shared QFS client. User applications or programs that generate these sparse (holey) files on shared QFS client systems by seeking ahead (or back), then writing data, will encounter this issue.
To determine if a file system is running in shared mode, look for the "shared" keyword in the host's "/etc/opt/SUNWsamfs/mcf" file (which is used by both the "SUNWqfs" and the "SUNWsamfs" packages).
Use either of the following commands to determine the Sun QFS or Sun SAM-FS version:
% pkginfo -l SUNWqfs PKGINST: SUNWqfs NAME: Sun QFS Solaris 2.9 CATEGORY: system ARCH: sparc VERSION: 4.0.5,REV=5.8.2002.07.29 % pkginfo -l SUNWsamfs PKGINST: SUNWsamfs NAME: Sun SAM-FS and Sun SAM-QFS software Solaris 2.8 CATEGORY: system ARCH: sparc VERSION: 4.0.5,REV=5.8.2002.07.29
Note: For more details please see the "Sun QFS, Sun SAM-FS, and Sun SAM-QFS File System Administrator's Guide".
For sparse files generated on the shared QFS client, data that is read from these files on either shared QFS clients or the shared QFS metadata server will contain information from whatever disk blocks happened to be associated with the file, and the file will appear corrupt. (There is actually no loss of written data).
The workaround is to not write sparse files from shared QFS client systems. Alternatively, sharing data out from the shared QFS metadata server via NFS should be considered. File security issues may require moving sensitive information from shared QFS to standard UFS(7FS) filesystems.
There are no further updates planned for this Sun Alert document. If
07-Apr-2008: no further updates. Resolved
Sun StorageTek SAM-FS 4.3 Software
This solution has no attachment