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.
References
Configurations
Configuration 1 (hide)
|
History
20 Nov 2024, 23:59
Type | Values Removed | Values Added |
---|---|---|
References | () http://securitytracker.com/id?1014751 - | |
References | () http://www.osvdb.org/19034 - | |
References | () http://www.redhat.com/support/errata/RHSA-2005-345.html - | |
References | () http://www.redhat.com/support/errata/RHSA-2005-346.html - | |
References | () http://www.redhat.com/support/errata/RHSA-2005-747.html - Patch, Vendor Advisory | |
References | () http://www.securityfocus.com/bid/14640 - | |
References | () https://exchange.xforce.ibmcloud.com/vulnerabilities/22316 - | |
References | () https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A9538 - |
Information
Published : 2005-08-23 04:00
Updated : 2025-04-03 01:03
NVD link : CVE-2005-2499
Mitre link : CVE-2005-2499
CVE.ORG link : CVE-2005-2499
JSON object : View
Products Affected
slocate
- slocate
CWE