Enterprise LinuxOperating system · Redhat
CVE-2013-4482
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedUntrusted 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidencepython-paste-script (paster) loads .egg-info files from the current working directory or its parent directories without validating the path, allowing a local attacker to place a malicious .egg-info file that gets executed with elevated privileges when the application is started via initscript.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Enterprise LinuxOperating system
= 6.0= 0.26.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- High
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/AC:H/Au:N/C:C/I:C/A:C
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify python-paste-script installationRun 'rpm -q python-paste-script' on RHEL/Scientific Linux to check if the package is installedAffected if package is installed and version matches RHEL 6.0 or Scientificlinux Luci 0.26.0
-
Identify initscript usage for pasterSearch for paster references in /etc/init.d/ or systemd service files using 'grep -r paster /etc/init.d/' and 'grep -r paster /etc/systemd/'Affected if an initscript or systemd service invokes paster commands
-
Check for .egg-info files in service run pathsExamine directories where services run (e.g., /var/www/, application root directories) for any .egg-info files using 'find / -name "*.egg-info" -type d 2>/dev/null'Affected if .egg-info directories exist in paths where paster initscripts execute
-
Verify directory permissions around paster executionInspect the working directories used by initscripts for paster: check if any are world-writable using 'ls -ld <directory>' and review initscript contents for 'cd' or 'WorkingDirectory' directivesAffected if paster runs from or accesses directories writable by non-root users
-
Confirm initscript runs as rootReview initscript for 'runuser' or 'sudo' commands, or check if service runs as root via 'grep -E "(User|RunAsUser)" /etc/systemd/system/*.service' or similar in init.d scriptsAffected if initscript executes paster with elevated (root) privileges
User is affected if python-paste-script is installed, runs via initscript with root privileges, and operates from directories containing or reachable to untrusted .egg-info files.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataAvoid running paster from untrusted directories; remove or secure the initscript to prevent execution from untrusted locations; implement explicit path validation to reject .egg-info files from untrusted locations.
Fix this in Enterprise Linux
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-4482 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2013-4482 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data