Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2024-7143: Insecure Inherited Permissions

0
Medium
VulnerabilityCVE-2024-7143cvecve-2024-7143
Published: Wed Aug 07 2024 (08/07/2024, 16:49:29 UTC)
Source: CVE Database V5

Description

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.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 03/20/2026, 22:32:57 UTC

Technical Analysis

CVE-2024-7143 is a vulnerability discovered in the Pulp package's role-based access control (RBAC) implementation. Pulp uses the AutoAddObjPermsMixin, specifically the add_roles_for_object_creator method, to assign permissions to the creator of an object upon its creation. However, when objects are created within a task context, the 'current authenticated user' is incorrectly determined by identifying the oldest user with any permissions on the task object rather than the actual user who dispatched or created the task. This results in all permissions for newly created objects being assigned to this oldest user, while the actual creator receives no permissions. This misassignment can lead to unauthorized access, as the oldest user may gain unintended privileges, and the true creator is denied access rights. The vulnerability has a CVSS v3.0 score of 6.7 (medium severity), reflecting its network attack vector, low attack complexity, requirement for high privileges, no user interaction, and impact on confidentiality and integrity with limited availability impact. No known exploits have been reported in the wild. The flaw affects Pulp versions prior to the fix and is particularly relevant for environments relying on task-based object creation and RBAC for permission management.

Potential Impact

The primary impact of CVE-2024-7143 is the incorrect assignment of permissions, which can lead to unauthorized access to sensitive objects created within tasks. The oldest user with permissions on a task may gain unintended access rights to objects they did not create or dispatch, potentially exposing confidential data or allowing unauthorized modifications. Conversely, the actual creator of the object is denied permissions, which can disrupt workflows and cause operational issues. This misassignment undermines the integrity of access controls and can lead to privilege escalation within organizations using Pulp. While availability impact is low, the confidentiality and integrity risks are significant, especially in environments where strict access controls are critical. Organizations relying on Pulp for content management, automation, or software distribution are at risk of unauthorized data exposure or manipulation if this vulnerability is exploited.

Mitigation Recommendations

To mitigate CVE-2024-7143, organizations should: 1) Apply patches or updates from the Pulp maintainers as soon as they become available to correct the RBAC logic. 2) Audit existing permissions on objects created within tasks to identify and remediate any misassigned permissions, ensuring that creators have appropriate access. 3) Implement monitoring and alerting for unusual permission changes or access patterns related to task-created objects. 4) Restrict task creation and permission assignment capabilities to trusted, minimal sets of users to reduce the risk of exploitation. 5) Review and harden RBAC policies to ensure that permission inheritance and assignment logic aligns with organizational security requirements. 6) Consider temporary compensating controls such as manual permission reviews or additional approval workflows for task-created objects until patches are applied. These steps go beyond generic advice by focusing on auditing and controlling the specific permission assignment flaw inherent in the vulnerability.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
redhat
Date Reserved
2024-07-26T18:48:08.747Z
Cvss Version
3.0
State
PUBLISHED

Threat ID: 691f82024f1c50aa2eb5ae92

Added to database: 11/20/2025, 9:02:58 PM

Last enriched: 3/20/2026, 10:32:57 PM

Last updated: 3/22/2026, 5:19:02 PM

Views: 93

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses