CVE-2024-7143: Pulpcore: rbac permissions incorrectly assigned in tasks that create objects
Noroxi assessment
Priority: Monitor (action score 33/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.60% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: automation-controller (Red Hat:ansible_automation_platform_developer:2.4::el8) 0:4.5.11-1.el8ap; automation-controller-cli (Red Hat:ansible_automation_platform_developer:2.4::el8) 0:4.5.11-1.el8ap; python39-urllib3 (Red Hat:ansible_automation_platform_developer:2.4::el8) 0:1.26.20-1.el8ap.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to automation-controller (Red Hat:ansible_automation_platform_developer:2.4::el8) 0:4.5.11-1.el8ap; automation-controller-cli (Red Hat:ansible_automation_platform_developer:2.4::el8) 0:4.5.11-1.el8ap; python39-urllib3 (Red Hat:ansible_automation_platform_developer:2.4::el8) 0:1.26.20-1.el8ap or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Aug 7, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.6% · 49th percentile
- CWE
- CWE-277
Report tools
Action score
33
Monitor
Low priority for now.
- CVSS
- 33 / 40 · 8.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.6%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 8.3
- CNA · redhat
- 6.7
- 1.6 point gap
CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:L
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| pulpproject | pulp | cpe:2.3:a:pulpproject:pulp |
| redhat | ansible automation platform | cpe:2.3:a:redhat:ansible_automation_platform |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- pulpproject pulpall versions
Versions reported by the vendor
Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.
github.com/pulp/pulpcore pulp
- up to and including 3.56.0affected · semver
Red Hat Red Hat Ansible Automation Platform 2
- all versionsaffected
- all versionsaffected
Red Hat Red Hat Satellite 6
- all versionsunknown
Red Hat Red Hat Update Infrastructure 4 for Cloud Providers
- all versionsunknown
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| PyPI | pulpcore | up to and including 3.56.0 | — |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | automation-controller | before 0:4.5.11-1.el8ap | 0:4.5.11-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | automation-controller-cli | before 0:4.5.11-1.el8ap | 0:4.5.11-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | python39-urllib3 | before 0:1.26.20-1.el8ap | 0:1.26.20-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | python3x-urllib3 | before 0:1.26.20-1.el8ap | 0:1.26.20-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | receptor | before 0:1.4.8-1.1.el8ap | 0:1.4.8-1.1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | receptorctl | before 0:1.4.8-1.1.el8ap | 0:1.4.8-1.1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el9 | automation-controller | before 0:4.5.11-1.el9ap | 0:4.5.11-1.el9ap |
| Red Hat:ansible_automation_platform_developer:2.4::el9 | automation-controller-cli | before 0:4.5.11-1.el9ap | 0:4.5.11-1.el9ap |
| Red Hat:ansible_automation_platform_developer:2.4::el9 | python-urllib3 | before 0:1.26.20-1.el9ap | 0:1.26.20-1.el9ap |
| Red Hat:ansible_automation_platform_developer:2.4::el9 | python3-urllib3 | before 0:1.26.20-1.el9ap | 0:1.26.20-1.el9ap |
| Red Hat:ansible_automation_platform_developer:2.4::el9 | receptor | before 0:1.4.8-1.1.el9ap | 0:1.4.8-1.1.el9ap |
| Red Hat:ansible_automation_platform_developer:2.4::el9 | receptorctl | before 0:1.4.8-1.1.el9ap | 0:1.4.8-1.1.el9ap |
| Red Hat:ansible_automation_platform:2.4::el8 | automation-controller-server | before 0:4.5.11-1.el8ap | 0:4.5.11-1.el8ap |
| Red Hat:ansible_automation_platform:2.4::el8 | automation-controller-ui | before 0:4.5.11-1.el8ap | 0:4.5.11-1.el8ap |
| Red Hat:ansible_automation_platform:2.4::el8 | automation-controller-venv-tower | before 0:4.5.11-1.el8ap | 0:4.5.11-1.el8ap |
| Red Hat:ansible_automation_platform:2.4::el8 | python39-django | before 0:4.2.16-1.el8ap | 0:4.2.16-1.el8ap |
| Red Hat:ansible_automation_platform:2.4::el8 | python39-pulpcore | before 0:3.28.32-1.el8ap | 0:3.28.32-1.el8ap |
| Red Hat:ansible_automation_platform:2.4::el8 | python3x-django | before 0:4.2.16-1.el8ap | 0:4.2.16-1.el8ap |
| Red Hat:ansible_automation_platform:2.4::el8 | python3x-pulpcore | before 0:3.28.32-1.el8ap | 0:3.28.32-1.el8ap |
| Red Hat:ansible_automation_platform:2.4::el9 | automation-controller-server | before 0:4.5.11-1.el9ap | 0:4.5.11-1.el9ap |
| Red Hat:ansible_automation_platform:2.4::el9 | automation-controller-ui | before 0:4.5.11-1.el9ap | 0:4.5.11-1.el9ap |
| Red Hat:ansible_automation_platform:2.4::el9 | automation-controller-venv-tower | before 0:4.5.11-1.el9ap | 0:4.5.11-1.el9ap |
| Red Hat:ansible_automation_platform:2.4::el9 | python-django | before 0:4.2.16-1.el9ap | 0:4.2.16-1.el9ap |
+3
Same product
pulpproject: all recordsOther highest-scoring records for the same primary product.
- CVE-2015-5263pulp-consumer-client 2.4.0 through 2.6.3 does not check the server's TLS certificate signatures when retrieving the server's public key upon32Monitor
- CVE-2016-3112client/consumer/cli.py in Pulp before 2.8.3 writes consumer private keys to etc/pki/pulp/consumer/consumer-cert.pem as world-readable, which31Monitor
- CVE-2018-1090In Pulp before version 2.16.2, secrets are passed into override_config when triggering a task and then become readable to all users with rea30Monitor
Published before and after this one in the same product
- ← EarlierCVE-2016-3108Jun 8, 2017 · The pulp-gen-nodes-certificate script in Pulp before 2.8.3 allows local users to leak the keys or write to arbitrary files via a symlink att28Monitor
- ← EarlierCVE-2016-3111Jun 8, 2017 · pulp.spec in the installation process for Pulp 2.8.3 generates the RSA key pairs used to validate messages between the pulp server and pulp 22Monitor
- ← EarlierCVE-2018-10917Aug 15, 2018 · pulp 2.16.x and possibly older is vulnerable to an improper path parsing.26Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| red hat:automation-controller | 0:4.5.11-1.el8ap · Red Hat:ansible_automation_platform_developer:2.4::el8 | Package registry (OSV) |
| red hat:automation-controller-cli | 0:4.5.11-1.el8ap · Red Hat:ansible_automation_platform_developer:2.4::el8 | Package registry (OSV) |
| red hat:automation-controller-server | 0:4.5.11-1.el8ap · Red Hat:ansible_automation_platform:2.4::el8 | Package registry (OSV) |
| red hat:automation-controller-ui | 0:4.5.11-1.el8ap · Red Hat:ansible_automation_platform:2.4::el8 | Package registry (OSV) |
| red hat:automation-controller-venv-tower | 0:4.5.11-1.el8ap · Red Hat:ansible_automation_platform:2.4::el8 | Package registry (OSV) |
| red hat:python39-django | 0:4.2.16-1.el8ap · Red Hat:ansible_automation_platform:2.4::el8 | Package registry (OSV) |
| red hat:python39-pulpcore | 0:3.28.32-1.el8ap · Red Hat:ansible_automation_platform:2.4::el8 | Package registry (OSV) |
| red hat:python39-urllib3 | 0:1.26.20-1.el8ap · Red Hat:ansible_automation_platform_developer:2.4::el8 | Package registry (OSV) |
| red hat:python3x-django | 0:4.2.16-1.el8ap · Red Hat:ansible_automation_platform:2.4::el8 | Package registry (OSV) |
| red hat:python3x-urllib3 | 0:1.26.20-1.el8ap · Red Hat:ansible_automation_platform_developer:2.4::el8 | Package registry (OSV) |
| red hat:receptor | 0:1.4.8-1.1.el8ap · Red Hat:ansible_automation_platform_developer:2.4::el8 | Package registry (OSV) |
| red hat:receptorctl | 0:1.4.8-1.1.el8ap · Red Hat:ansible_automation_platform_developer:2.4::el8 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-1186 · Aug 8, 2024(RedHat Pulp Güvenlik Bildirimi)
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- low · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- Low
Weakness class (CWE)
CWE-277 · Insecure Inherited PermissionsCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.