CVE-2015-5153
First published: Wed Jul 15 2015(Updated: )
It is reported by Austin Macdonald that pulp fails to properly remove existing permissions when an object is deleted (e.g. a user account), if an object with the same name is later created it will inherit the previous permissions leading to a potential privilege escalation. Please note that due to the manner in which pulp is used in Satellite6 it is not vulnerable.
Credit: secalert@redhat.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Pulpcore |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2015-5153?
CVE-2015-5153 is categorized as a medium severity vulnerability.
How do I fix CVE-2015-5153?
To fix CVE-2015-5153, ensure you apply the latest patches provided by the Pulp project.
What does CVE-2015-5153 allow an attacker to do?
CVE-2015-5153 allows an attacker to potentially escalate privileges due to improper permissions being retained after object deletion.
Which software versions are affected by CVE-2015-5153?
CVE-2015-5153 affects all versions of Pulp prior to the fix for this vulnerability.
What should I do if I cannot apply the fix for CVE-2015-5153 immediately?
If you cannot apply the fix for CVE-2015-5153 immediately, limit the creation of objects with existing names and monitor access logs for any anomalies.
- agent/type
- agent/first-publish-date
- collector/mitre-cve
- source/MITRE
- collector/redhat-bugzilla
- source/Red Hat
- alias/CVE-2015-5153
- agent/references
- agent/last-modified-date
- agent/weakness
- agent/severity
- agent/author
- agent/description
- agent/event
- agent/trending
- agent/source
- agent/tags
- agent/softwarecombine
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/pulp project
- canonical/pulpcore