ID CVE-2007-0227
Summary 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
Vulnerable Configurations
  • cpe:2.3:a:slocate:slocate:3.1:*:*:*:*:*:*:*
    cpe:2.3:a:slocate:slocate:3.1:*:*:*:*:*:*:*
CVSS
Base: 5.0 (as of 16-10-2018 - 16:31)
Impact:
Exploitability:
CWE NVD-CWE-Other
CAPEC
Access
VectorComplexityAuthentication
NETWORK LOW NONE
Impact
ConfidentialityIntegrityAvailability
PARTIAL NONE NONE
cvss-vector via4 AV:N/AC:L/Au:N/C:P/I:N/A:N
refmap via4
bid 21989
bugtraq
  • 20070110 Re: slocate leaks filenames of protected directories
  • 20070110 slocate leaks filenames of protected directories
  • 20070111 Re: slocate leaks filenames of protected directories
  • 20070112 Re: slocate leaks filenames of protected directories
  • 20070329 FLEA-2007-0005-1: slocate
osvdb 33465
ubuntu USN-425-1
statements via4
  • contributor Vincent Danen
    lastmodified 2007-01-19
    organization Mandriva
    statement Not vulnerable. This issue does not affect the versions of slocate as shipped with Mandriva Linux 2007.0 or earlier.
  • contributor Mark J Cox
    lastmodified 2007-01-18
    organization Red Hat
    statement Not vulnerable. This issue did not affect the versions of slocate as shipped with Red Hat Enterprise Linux 2.1, 3, or 4.
Last major update 16-10-2018 - 16:31
Published 13-01-2007 - 02:28
Back to Top