CVE-2007-0227: slocate 3.1 does not properly manage database entries that specify names of files in protected directories, wh

Routine

MEDIUM 5.0DOWNGRADE

CVE-2007-0227 is a medium-severity flaw (CVSS 5.0) affecting slocate. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 this priority

No elevated risk signals yet

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	5.0 (Medium)
EPSS exploit chance	1.7% (top 22%)
CISA exploited list	No
Published	2007-01-13
Last modified	2026-06-16

Publisher (CNA): MITRE · Vendor: slocate

Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2007-01-13 02:28 UTCPublished CVE record published
2026-06-16 22:35 UTCUpdated Record last modified

slocate slocate DOWNGRADE

Affected: 3.1

Fixed in: no fixed release known

Safe to downgrade to: a release before 3.1

1. Check installed version

apt-cache policy slocate || rpm -q slocate || slocate --version

2. No fixed release: DOWNGRADE to a release before 3.1 (Debian / Ubuntu)

apt-cache madison slocate sudo apt install slocate=<VERSION_BEFORE_3.1> sudo apt-mark hold slocate

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list slocate sudo dnf downgrade slocate-<VERSION_BEFORE_3.1> sudo dnf versionlock add slocate

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2007-0227?

slocate: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2007-0227 being exploited?

CVE-2007-0227 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2007-0227 affect?

CVE-2007-0227 affects slocate. Severity is medium (CVSS 5.0). 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 sl

How urgent is CVE-2007-0227?

Priority 37/100. No elevated risk signals yet.

Related CVEs

CVE-2003-0848 MEDIUM 4.6 DOWNGRADE Heap-based buffer overflow in main.c of slocate 2.6, and possibly other versions, may allow local users to gai
CVE-2003-0326 MEDIUM 4.6 MITIGATE Integer overflow in parse_decode_path() of slocate may allow attackers to execute arbitrary code via a LOCATE_
CVE-2003-0056 HIGH 7.2 DOWNGRADE Buffer overflow in secure locate (slocate) before 2.7 allows local users to execute arbitrary code via a long

References

← Back to latest CVEs