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
Configurations
History
No history.
Information
Published : 2007-01-13 02:28
Updated : 2018-10-16 16:31
NVD link : CVE-2007-0227
Mitre link : CVE-2007-0227
CVE.ORG link : CVE-2007-0227
JSON object : View
Products Affected
slocate
- slocate
CWE