How severe is CVE-2005-2499?

CVE-2005-2499 has a CVSS 2.0 base score of 2.1, rated low severity.

Is CVE-2005-2499 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (29th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2005-2499?

CVE-2005-2499 primarily affects Slocate. In total, 6 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2005-2499?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2005-2499 published?

CVE-2005-2499 was published on 2005-08-23 and last updated on 2026-06-16.

CVE-2005-2499

CVE-2005-2499 is a low-severity vulnerability in Slocate with a CVSS 2.0 base score of 2.1. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Low (CVSS 2.0 base score 2.1)
EPSS exploit prediction: 0% (29th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Slocate
Published: 2005-08-23
Last modified: 2026-06-16

Description

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.

Frequently asked questions

What is 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.
How severe is CVE-2005-2499?: CVE-2005-2499 has a CVSS 2.0 base score of 2.1, rated low severity.
Is CVE-2005-2499 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (29th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2005-2499?: CVE-2005-2499 primarily affects Slocate. In total, 6 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2005-2499?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2005-2499 published?: CVE-2005-2499 was published on 2005-08-23 and last updated on 2026-06-16.

References

Affected products (6)

cpe:2.3:a:slocate:slocate:2.1:*:*:*:*:*:*:*
cpe:2.3:a:slocate:slocate:2.2:*:*:*:*:*:*:*
cpe:2.3:a:slocate:slocate:2.3:*:*:*:*:*:*:*
cpe:2.3:a:slocate:slocate:2.4:*:*:*:*:*:*:*
cpe:2.3:a:slocate:slocate:2.5:*:*:*:*:*:*:*
cpe:2.3:a:slocate:slocate:2.6:*:*:*:*:*:*:*

More vulnerabilities in Slocate

CVE-2003-0056 — High (CVSS 7.2): Buffer overflow in secure locate (slocate) before 2.7 allows local users to execute arbitrary code via a long (1) -c or…
CVE-2007-0227 — Medium (CVSS 5.0): slocate 3.1 does not properly manage database entries that specify names of files in protected directories, which…
CVE-2003-0848 — Medium (CVSS 4.6): Heap-based buffer overflow in main.c of slocate 2.6, and possibly other versions, may allow local users to gain…
CVE-2003-0326 — Medium (CVSS 4.6): Integer overflow in parse_decode_path() of slocate may allow attackers to execute arbitrary code via a LOCATE_PATH with…

All CVEs affecting Slocate →