Pulp incorrectly assigns RBAC permissions in tasks that create objects
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.
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| Python (PyPI) | pulpcore | <= 3.56.0 | no fix |
References
- https://nvd.nist.gov/vuln/detail/CVE-2024-7143
- https://access.redhat.com/errata/RHSA-2024:6765
- https://access.redhat.com/security/cve/CVE-2024-7143
- https://bugzilla.redhat.com/show_bug.cgi?id=2300125
- https://github.com/pulp/pulpcore
- https://github.com/pulp/pulpcore/blob/93f241f34c503da0fbac94bdba739feda2636e12/pulpcore/tasking/_util.py#L108
- https://github.com/pulp/pulpcore/blob/main/CHANGES.md
- https://pypi.org/project/pulpcore
- https://github.com/advisories/GHSA-9m5j-4xx9-44j9
- CVSS vector
CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:L- Weakness (CWE)
CWE-277- Platform
- Python (PyPI)
- Package
pulpcore- Disclosed
- 07.08.2024
- Updated
- 11.10.2026 15:17
Sources and licenses
OSV / GitHub Advisory Database - PYSEC-2026-1808 - PyPA Advisory Database; CC BY 4.0
OSV / GitHub Advisory Database - GHSA-9m5j-4xx9-44j9 - CC BY 4.0
Vulnerability history: pulpcore
All published vulnerabilities of this package (Python (PyPI)), newest first. Shows whether this is a one-off slip or a package that needs watching.
This is the only known vulnerability of this package.
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.