CVE-2015-5153
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 · uneditedPulp does not remove permissions for named objects upon deletion, which allows authenticated users to gain the privileges of a deleted object via creating an object with the same 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 confidencePulp fails to clean up associated permissions when named objects are deleted, leaving orphaned ACL entries in the database. When a new object is created with the same name as a previously deleted object, it inadvertently inherits the old permissions, allowing authenticated users to gain elevated privileges through this permission inheritance mechanism.
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 dataall versionsCVSS 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
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 Pulp installation existsConfirm the Pulp service is running and the database is accessible. Identify the database backend in use (e.g., MongoDB) and locate the database connection configuration.Affected if Pulp is installed and using a database backend
-
Identify objects with potential orphaned permissionsQuery the database for permission/ACL records that reference objects which no longer exist in their respective collection tables. Compare permission records against active object records.Affected if Permission records exist for objects that have been deleted from the system
-
Check for duplicate permission records on recreated objectsQuery for objects that have multiple permission records, especially if the object creation timestamp differs significantly from the permission grant timestamp, indicating inherited permissions from a previously deleted object of the same name.Affected if Objects display permission records dated before their own creation timestamp
-
Test permission inheritance on object recreationCreate a test object, note its permissions, delete it, then create a new object with the exact same name and inspect whether it inherits any permissions from the deleted object.Affected if A newly created object with a previously used name inherits permissions not explicitly assigned to it
-
Verify deletion handler behaviorReview the code or configuration for object deletion handlers to confirm whether they include logic to remove associated permission/ACL records when objects are deleted.Affected if Deletion handlers do not explicitly remove associated permission records before deleting the object
The environment is affected if orphaned permission/ACL records exist in the database for deleted objects, or if recreated objects with previously used names inherit unexpected permissions.
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 dataImplement a deletion handler that properly removes all permission/ACL records associated with objects upon deletion, and add validation during object creation to reject or clean up any orphaned permissions for objects of the same name.
- Consultation3.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,720.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-5153 — 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-5153 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