CVE-2010-2945 json
The default configuration of SLiM before 1.3.2 places ./ (dot slash) at the beginning of the default_path option, which might allow local u…
published 16y ago modified 4mo ago also EUVD-2010-2949
- cvss
- 6.9
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 22%
- public exploits
- 0
- none known
Summary
The default configuration of SLiM before 1.3.2 places ./ (dot slash) at the beginning of the default_path option, which might allow local users to gain privileges via a Trojan horse program in the current working directory, related to slim.conf and cfg.cpp.
Patch / fix
- slim Debian 14, Debian 13, Debian 12 1.3.1-7
debian advisories DEBIAN-CVE-2010-2945
Is CVE-2010-2945 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2010-2945 updated
slim: insecure PATH assignment
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.30% chance of exploitation in the next 30 days, higher than 22% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.9 | AV:L/AC:M/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-16 Configuration
References
-
secunia.com
/advisories/41005
third-party-advisory, vendor-advisory
-
openwall.com
/lists/oss-security/2010/08/20/10
mailing-list
- svn.berlios.de /viewvc/slim?view=revision&revision=171
-
openwall.com
/lists/oss-security/2010/08/19/8
mailing-list
Sources
- CVE List CVE-2010-2945
- NVD CVE-2010-2945
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.