slocate 3.1 does not properly manage database entries that specify names of files in…
Priority LOW 26Published · Updated
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- — Not recorded in CVSS 2.0
- Attack complexity
- Low
- Impact type
- —
- Confidentiality · integrity · availability
- Partial · None · None
- Fix status
- No fix listed
Attack profile from CVSS 2.0 · NVD. Fix status from CNA.
Summary
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.
Why it matters now
EPSS 0.0174 77th percentileScored 2026-11-07
Fix No fix listed No fixed version in the sources yet
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | — | all versions | — | No fix listed | CNA |
- — Vendor— Affected all versions Fixed in — No fix listed CNA
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-02 Threatist record created from CVE-2007-0227
- 2026-10-03 Alias added: GHSA-77x2-7r55-3gw2
More Slocate vulnerabilities
- TI-2003-00052 Buffer overflow in secure locate (slocate) before 2.7 allows local users to execute… CVSS 2.0HIGH 7.2
- TI-2003-00783 Heap-based buffer overflow in main.c of slocate 2.6, and possibly other versions, may… CVSS 2.0MEDIUM 4.6
- TI-2003-00306 Integer overflow in parse_decode_path() of slocate may allow attackers to execute… CVSS 2.0MEDIUM 4.6
- TI-2005-02365 slocate before 2.7 does not properly process very long paths, which allows local users to… CVSS 2.0LOW 2.1
Sources
- CVE-2007-0227 · CVE Program
- CVE-2007-0227 · NVD
- FIRST EPSS
- GHSA-77x2-7r55-3gw2 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences