This page aggregates publicly disclosed CVE and security risk information related to slocate, with CVSS, EPSS, publication dates, and vulnerability intelligence data to help assess potential risk and remediation priority.
| CVE | 概要 | ソース | CVSS 最大値 | EPSS（%） | 公開 | 更新 |
|---|---|---|---|---|---|---|
| CVE-2007-0227 | 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. | [email protected] | 5.0 | 1.67% | 2007-01-12 | 2026-06-16 |
| CVE-2005-2499 | 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. | [email protected] | 2.1 | 0.37% | 2005-08-23 | 2026-06-16 |
| CVE-2003-0848 | 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. | [email protected] | 4.6 | 0.94% | 2003-11-17 | 2026-06-16 |
| CVE-2003-0326 | 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. | [email protected] | 4.6 | 0.40% | 2003-06-09 | 2026-06-16 |
| CVE-2003-0056 | 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. | [email protected] | 7.2 | 1.09% | 2003-02-19 | 2026-06-16 |