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.

An updated slocate package that fixes a denial of service and various bugs is available.

This update has been rated as having low security impact by the Red Hat Security Response Team.

Slocate is a security-enhanced version of locate. Like locate, slocate searches through a central database (updated nightly) for files that match a given pattern. Slocate allows you to quickly find files anywhere on your system.

A bug was found in the way slocate scans the local filesystem. A carefully prepared directory structure could cause updatedb's file system scan to fail silently, resulting in an incomplete slocate database. The Common Vulnerabilities and Exposures project has assigned the name CVE-2005-2499 to this issue.

Additionally this update addresses the following issues :

  - File system type exclusions were processed only when     starting updatedb and did not reflect file systems     mounted while updatedb was running (for example,     automounted file systems.)

  - File system type exclusions were ignored for file     systems that were mounted to a path containing a     symbolic link.

  - Databases created by slocate were owned by the slocate     group even if they were created by regular users.

  - The default configuration excluded /mnt/floppy, but not     /media.

  - The default configuration did not exclude nfs4 file     systems.

Users of slocate are advised to upgrade to this updated package, which contains backported patches and is not affected by these issues.

An updated slocate package that fixes a denial of service and various bugs is now available.

This update has been rated as having low security impact by the Red Hat Security Response Team.

Slocate is a security-enhanced version of locate. Like locate, slocate searches through a central database (updated nightly) for files that match a given pattern. Slocate allows you to quickly find files anywhere on your system.

A bug was found in the way slocate scans the local filesystem. A carefully prepared directory structure could cause updatedb's file system scan to fail silently, resulting in an incomplete slocate database. The Common Vulnerabilities and Exposures project has assigned the name CVE-2005-2499 to this issue.

Additionally this update addresses the following issues :

  - Files with a size of 2 GB and larger were not entered     into the slocate database.

  - File system type exclusions were processed only when     starting updatedb and did not reflect file systems     mounted while updatedb was running (for example,     automounted file systems).

  - File system type exclusions were ignored for file     systems that were mounted to a path containing a     symbolic link.

  - Databases created by slocate were owned by the slocate     group even if they were created by regular users.

Users of slocate are advised to upgrade to this updated package, which contains backported patches and is not affected by these issues.

The remote Redhat Enterprise Linux 4 host has a package installed that is affected by a vulnerability as referenced in the RHSA-2005:346 advisory.

    Slocate is a security-enhanced version of locate. Like locate, slocate     searches through a central database (updated nightly) for files that match     a given pattern. Slocate allows you to quickly find files anywhere on your     system.

    A bug was found in the way slocate scans the local filesystem. A carefully     prepared directory structure could cause updatedb's file system scan to     fail silently, resulting in an incomplete slocate database. The Common     Vulnerabilities and Exposures project has assigned the name CAN-2005-2499     to this issue.

    Additionally this update addresses the following issues:

    - File system type exclusions were processed only when starting updatedb       and did not reflect file systems mounted while updatedb was running       (for example, automounted file systems.)

    - File system type exclusions were ignored for file systems that were       mounted to a path containing a symbolic link.

    - Databases created by slocate were owned by the slocate group even if they       were created by regular users.

    - The default configuration excluded /mnt/floppy, but not /media.

    - The default configuration did not exclude nfs4 file systems.

    Users of slocate are advised to upgrade to this updated package, which     contains backported patches and is not affected by these issues.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

A bug was discovered in the way that slocate processes very long paths. A local user could create a carefully crafted directory structure that would prevent updatedb from completing its filesystem scan, resulting in an incomplete database.

An updated slocate package that fixes a denial of service issue is now available.

This update has been rated as having low security impact by the Red Hat Security Response Team.

Slocate is a security-enhanced version of locate. Like locate, slocate searches through a nightly-updated central database for files that match a given pattern.

A bug was found in the way slocate processes very long paths. A local user could create a carefully crafted directory structure that would prevent updatedb from completing its file system scan, resulting in an incomplete slocate database. The Common Vulnerabilities and Exposures project has assigned the name CVE-2005-2499 to this issue.

Users are advised to upgrade to this updated package, which includes a backported patch to resolve this issue.

A carefully prepared directory structure could stop the updatedb file system scan, resulting in an incomplete slocate database. The Common Vulnerabilities and Exposures project has assigned the name CVE-2005-2499 to this issue.

Note that Tenable Network Security has extracted the preceding description block directly from the Fedora security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

ID	Name	Product	Family	Severity
21925	CentOS 4 : slocate (CESA-2005:346)	Nessus	CentOS Local Security Checks	low
21808	CentOS 3 : slocate (CESA-2005:345)	Nessus	CentOS Local Security Checks	low
19986	RHEL 4 : slocate (RHSA-2005:346)	Nessus	Red Hat Local Security Checks	medium
19903	Mandrake Linux Security Advisory : slocate (MDKSA-2005:147)	Nessus	Mandriva Local Security Checks	low
19828	RHEL 3 : slocate (RHSA-2005:345)	Nessus	Red Hat Local Security Checks	low
19490	RHEL 2.1 : slocate (RHSA-2005:747)	Nessus	Red Hat Local Security Checks	low
19481	Fedora Core 3 : slocate-2.7-12.fc3.1 (2005-771)	Nessus	Fedora Local Security Checks	low
19480	Fedora Core 4 : slocate-2.7-22.fc4.1 (2005-770)	Nessus	Fedora Local Security Checks	low

Detections

Analytics

CVE-2005-2499

medium

Tenable Plugins

low

low

medium

low

low

low

low

low