Object permission misassignment via incorrect task creator
Published Aug 7, 2024 · Updated Jun 2, 2026
Authorization failure in pulpcore before 3.56.0 allows remote authenticated users to misassign object permissions during tasks. AutoAddObjPermsMixin resolves a task-created object's creator from the first user holding any task permission, rather than the user who dispatched the task. The path requires a task that creates an RBAC object with automatic creator-role assignment; permissions go to the oldest eligible user while the actual creator receives none.
Summary
What happened
Authorization failure in pulpcore before 3.56.0 allows remote authenticated users to misassign object permissions during tasks. AutoAddObjPermsMixin resolves a task-created object's creator from the first user holding any task permission, rather than the user who dispatched the task. The path requires a task that creates an RBAC object with automatic creator-role assignment; permissions go to the oldest eligible user while the actual creator receives none.
The record
- CVE
- CVE-2024-7143
- Published
- Aug 7, 2024
- Updated
- Jun 2, 2026
- Vendor
- The Pulp Project
- Product
- Pulpcore
- Classifications
- CWE-277
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Aug 7, 2024CVE publishedPublication date reported by the CVE source.
- Jun 2, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=3.56.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo