FedoraOperating system · Fedoraproject
CVE-2015-1815
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 · uneditedThe get_rpm_nvr_by_file_path_temporary function in util.py in setroubleshoot before 3.2.22 allows remote attackers to execute arbitrary commands via shell metacharacters in a file name.
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 confidenceThis is a command injection vulnerability in the setroubleshoot SELinux troubleshooting tool. The get_rpm_nvr_by_file_path_temporary function in util.py fails to sanitize shell metacharacters in filenames before passing them to shell commands, allowing remote attackers to inject and execute arbitrary OS commands.
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
FedoraOperating system
= 22<= 3.2.21CVSS 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
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/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.
-
Check if setroubleshoot package is installedRun 'rpm -q setroubleshoot' on Fedora-based systemsAffected if The package is not installed or the command returns an error indicating the package is missing
-
Determine installed setroubleshoot versionRun 'rpm -q --info setroubleshoot' and look for the Version field in the outputAffected if The version returned is 3.2.21 or lower
-
Verify vulnerable code path existsLocate util.py in the setroubleshoot installation (typically in /usr/share/setroubleshoot or via 'rpm -ql setroubleshoot') and check if the function get_rpm_nvr_by_file_path_temporary is presentAffected if The function exists in the installed version, indicating the vulnerable code path is present
-
Check if setroubleshoot service is activeRun 'systemctl status setroubleshoot' or check if the SELinux troubleshooting daemon processes are runningAffected if The setroubleshoot service is running and actively processing SELinux events, which would trigger the vulnerable function when analyzing file paths
A system is affected if setroubleshoot version 3.2.21 or earlier is installed and the vulnerable function exists in the codebase, with increased risk if the setroubleshoot service is actively processing SELinux audit events.
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.
dbcve · scopedUpgrade setroubleshoot to version 3.2.22 or later. Until then, restrict access to systems running vulnerable versions and monitor for suspicious filename patterns containing characters like ;, |, &, $, or backticks.
setroubleshoot version 3.2.22 or later
- Update the Fedora 22 package metadata: dnf check-update or yum check-update
- Upgrade setroubleshoot to version 3.2.22 or later: dnf upgrade setroubleshoot or yum update setroubleshoot
- Verify the installed version is 3.2.22 or higher: rpm -q setroubleshoot
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Fedora
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-1815 — 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-2015-1815 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