Slocate
by Slocate
CVEs (5)
| CVE | Vendor / Product | Sev | Risk | CVSS | EPSS | KEV | Published | Description |
|---|---|---|---|---|---|---|---|---|
| CVE-2003-0848 | 0.03 | — | 0.01 | Nov 17, 2003 | 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-0056 | 0.03 | — | 0.01 | Feb 19, 2003 | 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. | |||
| CVE-2007-0227 | 0.00 | — | 0.02 | Jan 13, 2007 | 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. | |||
| CVE-2005-2499 | 0.00 | — | 0.00 | Aug 23, 2005 | 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-0326 | 0.00 | — | 0.00 | Jun 9, 2003 | 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-0848Nov 17, 2003risk 0.03cvss —epss 0.01
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-0056Feb 19, 2003risk 0.03cvss —epss 0.01
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.
- CVE-2007-0227Jan 13, 2007risk 0.00cvss —epss 0.02
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.
- CVE-2005-2499Aug 23, 2005risk 0.00cvss —epss 0.00
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-0326Jun 9, 2003risk 0.00cvss —epss 0.00
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.