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
21 Nov 2024, 00:25
Type | Values Removed | Values Added |
---|---|---|
References | () http://osvdb.org/33465 - | |
References | () http://www.securityfocus.com/archive/1/456489/100/0/threaded - | |
References | () http://www.securityfocus.com/archive/1/456530/100/0/threaded - | |
References | () http://www.securityfocus.com/archive/1/456593/100/0/threaded - | |
References | () http://www.securityfocus.com/archive/1/456739/100/0/threaded - | |
References | () http://www.securityfocus.com/archive/1/464220/30/7320/threaded - | |
References | () http://www.securityfocus.com/bid/21989 - | |
References | () http://www.ubuntu.com/usn/usn-425-1 - |
Information
Published : 2007-01-13 02:28
Updated : 2025-04-09 00:30
NVD link : CVE-2007-0227
Mitre link : CVE-2007-0227
CVE.ORG link : CVE-2007-0227
JSON object : View
Products Affected
slocate
- slocate
CWE