Approved changes feed: RSS · Atom
cpe:2.3:a:pulpproject:pulp:-:*:*:*:*:*:*:*
part: a version: - update: *
| Vendor | Pulpproject (2029ae56-dee8-5e4a-91d9-7975876ff3ae) |
|---|---|
| Product | Pulp (916f1cd5-8b11-5cee-89dc-95f039be43f4) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from purl2cpe mapping |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/pulp/pulp |
purl2cpe | 2026-06-01 10:11:22.154611 |
pkg:pypi/pulp-container |
purl2cpe | 2026-06-01 10:11:22.154614 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2024-7143 |
vulnerable | 2026-06-08 06:58:21.357718 |
Pulpcore: rbac permissions incorrectly assigned in tasks that create objects
MEDIUM (6.7)
A flaw was found in the Pulp package. When a role-based access control (RBAC) object in Pulp is set to assign permissions on its creation, it uses the `AutoAddObjPermsMixin` (typically the add_roles_for_object_creator method). This method finds the object creator by checking the current authenticated user. For objects that are created within a task, this current user is set by the first user with any permissions on the task object. This means the oldest user with model/domain-level task permissions will always be set as the current user of a task, even if they didn't dispatch the task. Therefore, all objects created in tasks will have their permissions assigned to this oldest user, and the creating user will receive nothing.
Published: 2024-08-07T16:49:29.842Z
Updated: 2026-06-02T15:17:14.856Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.