Slocate is a file-location and search utility that maintains a modest vulnerability profile centered on its single core product. The reported exposure reflects application-level issues common to command-line search and indexing tools; live severity, exploitation, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Slocate over time
Signals from CVEs in this vendor scope (5 CVEs).
5 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2003-0056HIGH 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. | Feb 19, 2003 | 7.2 | 27 | NO | YES |
CVE-2003-0848MEDIUM 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 "p | Nov 17, 2003 | 4.6 | 24 | NO | YES |
CVE-2007-0227MEDIUM 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: an | Jan 13, 2007 | 5.0 | 18 | NO | NO |
CVE-2003-0326MEDIUM 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 use | Jun 9, 2003 | 4.6 | 14 | NO | NO |
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 cr | Aug 23, 2005 | 2.1 | 11 | NO | NO |
Signals from CVEs in this vendor scope (5 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Slocate.
Media articles that mention a CVE ID that affects a product developed by Slocate — matched by CVE ID, not by vendor name.