Slocate

slocate

Vendor: Slocate • 5 CVEs

CVEs (5)

CVE VENDORS PRODUCTS UPDATED PUBLISHED CVSS
CVE-2007-0227 1Slocate 1Slocate Apr 23, 2026 Jan 13, 2007 N/A· v4 N/A· v3 5.0 MEDIUM· v2 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...Show more 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.Show less
CVE-2005-2499 1Slocate 1Slocate Apr 16, 2026 Aug 23, 2005 N/A· v4 N/A· v3 2.1 LOW· v2 slocate before 2.7 does not properly process very long paths, which allows local users to cause a denial of service (updatedb exit and incomplete slocate database) via a certain crafted directory structure.
CVE-2003-0848 1Slocate 1Slocate Apr 16, 2026 Nov 17, 2003 N/A· v4 N/A· v3 4.6 MEDIUM· v2 Heap-based buffer overflow in main.c of slocate 2.6, and possibly other versions, may allow local users to gain privileges via a modified slocate database that causes a negative "pathlen" value to be used.
CVE-2003-0326 1Slocate 1Slocate Apr 16, 2026 Jun 9, 2003 N/A· v4 N/A· v3 4.6 MEDIUM· v2 Integer overflow in parse_decode_path() of slocate may allow attackers to execute arbitrary code via a LOCATE_PATH with a large number of ":" (colon) characters, whose count is used in a call to malloc.
CVE-2003-0056 1Slocate 1Slocate Apr 16, 2026 Feb 19, 2003 N/A· v4 N/A· v3 7.2 HIGH· v2 Buffer overflow in secure locate (slocate) before 2.7 allows local users to execute arbitrary code via a long (1) -c or (2) -r command line argument.