CVE-2024-7143: Insecure Inherited Permissions
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 Analysis
Technical Summary
CVE-2024-7143 is a vulnerability in the Pulp package's role-based access control (RBAC) mechanism, specifically in how permissions are assigned to objects created within tasks. Pulp uses the AutoAddObjPermsMixin, typically the add_roles_for_object_creator method, to assign permissions to the creator of an object by identifying the current authenticated user. However, when objects are created inside tasks, the 'current user' is incorrectly set to the oldest user with any model or domain-level permissions on the task object, rather than the actual user who dispatched or created the task. As a result, permissions for newly created objects are assigned to this oldest user, while the actual creator receives no permissions. This flaw can lead to unauthorized access where an unintended user gains control over objects they did not create, potentially enabling privilege escalation or unauthorized data access. The vulnerability requires an authenticated user with some level of task permissions but does not require user interaction. The CVSS 3.0 score is 6.7, indicating medium severity, with network attack vector, low attack complexity, high confidentiality and integrity impact, and low availability impact. No known exploits are currently reported in the wild. The flaw affects all versions of Pulp prior to the fix and is particularly relevant in environments where Pulp is used for content management, software distribution, or automation tasks.
Potential Impact
For European organizations, this vulnerability poses a risk of unauthorized access and privilege escalation within systems using Pulp for package management or content distribution. Misassigned permissions could allow an unintended user to access, modify, or control objects they should not have rights to, potentially leading to data breaches or operational disruptions. Confidentiality and integrity of sensitive data managed by Pulp could be compromised. Organizations relying on automated task workflows may experience permission inconsistencies, complicating audit and compliance efforts under regulations such as GDPR. The impact is heightened in sectors with strict data governance requirements, including finance, healthcare, and government. Although availability impact is low, the trustworthiness and security posture of affected systems could be undermined, increasing risk exposure. The requirement for authenticated users with task permissions limits exploitation scope but does not eliminate risk, especially in environments with multiple administrators or users with elevated privileges.
Mitigation Recommendations
To mitigate CVE-2024-7143, organizations should first audit and review current task-level permissions within Pulp, ensuring only trusted and necessary users have such privileges. Implement strict role separation and least privilege principles to minimize the number of users with task permissions. Monitor and log task creation and permission assignments to detect anomalies. Apply any available patches or updates from Pulp maintainers promptly once released. If patches are not yet available, consider implementing compensating controls such as restricting task creation to a limited set of users or disabling automated task workflows where feasible. Conduct regular permission reviews and access control audits to identify and correct misassignments. Educate administrators on the implications of task permissions and the importance of proper RBAC configuration. Finally, integrate Pulp security monitoring into broader organizational security operations to detect potential misuse stemming from this vulnerability.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden
CVE-2024-7143: Insecure Inherited Permissions
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
Technical Analysis
CVE-2024-7143 is a vulnerability in the Pulp package's role-based access control (RBAC) mechanism, specifically in how permissions are assigned to objects created within tasks. Pulp uses the AutoAddObjPermsMixin, typically the add_roles_for_object_creator method, to assign permissions to the creator of an object by identifying the current authenticated user. However, when objects are created inside tasks, the 'current user' is incorrectly set to the oldest user with any model or domain-level permissions on the task object, rather than the actual user who dispatched or created the task. As a result, permissions for newly created objects are assigned to this oldest user, while the actual creator receives no permissions. This flaw can lead to unauthorized access where an unintended user gains control over objects they did not create, potentially enabling privilege escalation or unauthorized data access. The vulnerability requires an authenticated user with some level of task permissions but does not require user interaction. The CVSS 3.0 score is 6.7, indicating medium severity, with network attack vector, low attack complexity, high confidentiality and integrity impact, and low availability impact. No known exploits are currently reported in the wild. The flaw affects all versions of Pulp prior to the fix and is particularly relevant in environments where Pulp is used for content management, software distribution, or automation tasks.
Potential Impact
For European organizations, this vulnerability poses a risk of unauthorized access and privilege escalation within systems using Pulp for package management or content distribution. Misassigned permissions could allow an unintended user to access, modify, or control objects they should not have rights to, potentially leading to data breaches or operational disruptions. Confidentiality and integrity of sensitive data managed by Pulp could be compromised. Organizations relying on automated task workflows may experience permission inconsistencies, complicating audit and compliance efforts under regulations such as GDPR. The impact is heightened in sectors with strict data governance requirements, including finance, healthcare, and government. Although availability impact is low, the trustworthiness and security posture of affected systems could be undermined, increasing risk exposure. The requirement for authenticated users with task permissions limits exploitation scope but does not eliminate risk, especially in environments with multiple administrators or users with elevated privileges.
Mitigation Recommendations
To mitigate CVE-2024-7143, organizations should first audit and review current task-level permissions within Pulp, ensuring only trusted and necessary users have such privileges. Implement strict role separation and least privilege principles to minimize the number of users with task permissions. Monitor and log task creation and permission assignments to detect anomalies. Apply any available patches or updates from Pulp maintainers promptly once released. If patches are not yet available, consider implementing compensating controls such as restricting task creation to a limited set of users or disabling automated task workflows where feasible. Conduct regular permission reviews and access control audits to identify and correct misassignments. Educate administrators on the implications of task permissions and the importance of proper RBAC configuration. Finally, integrate Pulp security monitoring into broader organizational security operations to detect potential misuse stemming from this vulnerability.
Affected Countries
For access to advanced analysis and higher rate limits, contact root@offseq.com
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: 11/20/2025, 9:19:46 PM
Last updated: 11/23/2025, 7:02:47 PM
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2025-13564: Denial of Service in SourceCodester Pre-School Management System
MediumCVE-2025-13562: Command Injection in D-Link DIR-852
MediumCVE-2025-13561: SQL Injection in SourceCodester Company Website CMS
MediumCVE-2025-54515: CWE-1284 Improper Validation of Specified Quantity in Input in AMD Versal™ Adaptive SoC Devices
LowCVE-2025-48507: CWE-1284 Improper Validation of Specified Quantity in Input in AMD Kria™ SOM
HighActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.