Approved changes feed: RSS · Atom
cpe:2.3:a:slocate:slocate:3.1:*:*:*:*:*:*:*part: a version: 3.1 update: *
| Vendor | Slocate (136bebdd-4c1f-51cf-bea7-8889a2fccc6f) |
|---|---|
| Product | Slocate (91c58890-c3c5-5bc5-a070-1fdad04afb47) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2007-0227 |
vulnerable | 2026-06-08 04:49:31.724430 |
Details available
slocate 3.1 does not properly manage database entries that specify names of files in protected directories, which allows local users to obtain the names of private files. NOTE: another researcher reports that the issue is not present in slocate 2.7.
Published: 2007-01-13T02:00:00.000Z
Updated: 2024-08-07T12:12:17.521Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.