"value":"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."
},
{
"lang":"es",
"value":"slocate 3.1 no maneja adecuadamente la direcci\u00f3n de entradas en la base de datos que especifica nombres de campos en directorios protegidos, lo cual permiten a un usuario local obtener los nombres de ficheros privados. NOTA: otros investigadores informan que este asunto no est\u00e1 presente en slocate 2.7."
}
],
"vendorComments":[
{
"organization":"Red Hat",
"comment":"Not vulnerable. This issue did not affect the versions of slocate as shipped with Red Hat Enterprise Linux 2.1, 3, or 4.\n",
"lastModified":"2007-01-18T00:00:00"
},
{
"organization":"Mandriva",
"comment":"Not vulnerable. This issue does not affect the versions of slocate as shipped with Mandriva Linux 2007.0 or earlier.",