CVE-2005-2499
Slocate vulnerability
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.
Affected products
Slocate. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Slocate runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- www.redhat.com/support/errata/RHSA-2005-747.html · Patch
- securitytracker.com/id?1014751
- www.osvdb.org/19034
- www.redhat.com/support/errata/RHSA-2005-345.html
- www.redhat.com/support/errata/RHSA-2005-346.html
- www.securityfocus.com/bid/14640
- exchange.xforce.ibmcloud.com/vulnerabilities/22316
- oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A9538
- nvd.nist.gov/vuln/detail/CVE-2005-2499
- cve.org/CVERecord?id=CVE-2005-2499
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.