Secure Locate (slocate) allows local users to corrupt memory via a malformed database file that specifies an offset value that accesses memory outside of the intended buffer.
CVE-2001-0066 is a security vulnerability that . Impacting 1 product from kevin_lindsay organizations running these solutions should prioritize assessment and patching.
Originally identified in 2001, this vulnerability predates many modern security frameworks and practices. The vulnerability landscape of that era was characterized by different threat models and less mature defense mechanisms compared to contemporary standards.
2001-02-16T05:00:00.000
2025-04-03T01:03:51.193
Deferred
CVSSv2: 7.2 (HIGH)
AV:L/AC:L/Au:N/C:C/I:C/A:C
3.9
10.0
| Type | Vendor | Product | Version/Range | Vulnerable? |
|---|---|---|---|---|
| Application | kevin_lindsay | secure_locate | 1.4 | Yes |
| Application | kevin_lindsay | secure_locate | 1.5 | Yes |
| Application | kevin_lindsay | secure_locate | 1.6 | Yes |
| Application | kevin_lindsay | secure_locate | 2.0 | Yes |
| Application | kevin_lindsay | secure_locate | 2.1 | Yes |
| Application | kevin_lindsay | secure_locate | 2.2 | Yes |
SecUtils normalizes and enriches National Vulnerability Database (NVD) records by standardizing vendor and product identifiers, aggregating vulnerability metadata from both NVD and MITRE sources, and providing structured context for security teams. For kevin_lindsay's affected products, we extract Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) classifications, CVSS severity metrics, and reference data to enable rapid vulnerability prioritization and asset correlation. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for patch management, risk assessment, and security operations.