CVE-2013-4482 json
Untrusted search path vulnerability in python-paste-script (aka paster) in Luci 0.26.0, when started using the initscript, allows local use…
published 12y ago modified 4mo ago also EUVD-2013-4347
- cvss
- 6.2
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 32%
- public exploits
- 0
- none known
Summary
Untrusted search path vulnerability in python-paste-script (aka paster) in Luci 0.26.0, when started using the initscript, allows local users to gain privileges via a Trojan horse .egg-info file in the (1) current working directory or (2) its parent directories.
Patch / fix
- luci RHEL 6 0.26.0-48.el6
red hat advisories RHSA-2013:1603
Is CVE-2013-4482 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-2013-4482 updated cvss 3.7
luci: paster hidden untrusted path and "command" (callable association) injection
-
Red Hat Enterprise Linux High Availability (v. 6) luci 0.26.0-48.el6 Red Hat Enterprise Linux Resilient Storage (v. 6) luci 0.26.0-48.el6fixed: vendor fix RHSA-2013:1603
-
Red Hat Enterprise Linux 5 conganot 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.38% chance of exploitation in the next 30 days, higher than 32% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.2 | AV:L/AC:H/Au:N/C:C/I:C/A:C |
References
Sources
- CVE List CVE-2013-4482
- NVD CVE-2013-4482
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.