Description
slocate 3.1 does not properly manage database entries that specify names of files in protected directories, which allows local users to obtain the names of private files. NOTE: another researcher reports that the issue is not present in slocate 2.7.
References
- 33465 vdb-entry
- 20070112 Re: slocate leaks filenames of protected directories mailing-list
- 21989 vdb-entry
- 20070110 Re: slocate leaks filenames of protected directories mailing-list
- 20070110 slocate leaks filenames of protected directories mailing-list
- 20070111 Re: slocate leaks filenames of protected directories mailing-list
- 20070329 FLEA-2007-0005-1: slocate mailing-list
- USN-425-1 vendor-advisory