Insecure Inherited Permissions Affecting python-pulpcore package, versions *


Severity

Recommended
0.0
medium
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.61% (49th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL10-PYTHONPULPCORE-9837042
  • published28 Apr 2025
  • disclosed7 Aug 2024

Introduced: 7 Aug 2024

CVE-2024-7143  (opens in a new tab)
CWE-277  (opens in a new tab)

How to fix?

There is no fixed version for RHEL:10 python-pulpcore.

NVD Description

Note: Versions mentioned in the description apply only to the upstream python-pulpcore package and not the python-pulpcore package as distributed by RHEL. See How to fix? for RHEL:10 relevant fixed versions and status.

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.

CVSS Base Scores

version 3.1