PatchTheCVEslocate vulnerabilities and fixes
Recent CVEs affecting slocate, with upgrade or downgrade steps. 4 tracked.
slocate has 4 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2007-01-13. Highest priority: CVE-2003-0056 (score 47/100).
- CVE-2007-0227 MEDIUM 5.0 DOWNGRADE slocate 3.1 does not properly manage database entries that specify names of files in protected directories, wh
- CVE-2003-0848 MEDIUM 4.6 DOWNGRADE Heap-based buffer overflow in main.c of slocate 2.6, and possibly other versions, may allow local users to gai
- CVE-2003-0326 MEDIUM 4.6 MITIGATE Integer overflow in parse_decode_path() of slocate may allow attackers to execute arbitrary code via a LOCATE_
- CVE-2003-0056 HIGH 7.2 DOWNGRADE Buffer overflow in secure locate (slocate) before 2.7 allows local users to execute arbitrary code via a long
FAQ
How do I fix slocate vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is slocate being exploited right now?
None of the tracked slocate CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which slocate CVE should I patch first?
CVE-2003-0056 currently ranks highest (47/100): Buffer overflow in secure locate (slocate) before 2.7 allows local users to execute arbitrary code via a long .