# CVE-2024-7143: Pulpcore: rbac permissions incorrectly assigned in tasks that create objects

> Incorrect RBAC assignment in Pulp tasks grants object creation permissions to the wrong user, allowing unauthorized privilege escalation and data modification.

- **Severity:** Medium 6.7 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Aug 2024
- **Updated:** 2 Jun 2026
- **Also known as:** GHSA-9m5j-4xx9-44j9, PYSEC-2026-1808

## What is CVE-2024-7143?

CVE-2024-7143 is a medium-severity missing authorization vulnerability in Red Hat Ansible Automation Platform 2, published on 7 Aug 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official 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.

Weakness: CWE-277 (Insecure Inherited Permissions)

## Which versions are affected by CVE-2024-7143?

3 open source packages ship an affected version, including pulpcore. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pulpcore` | PyPI | All versions to 3.56.0 | None |
| `pulpcore` | PyPI | All versions to 3.56.0 | None |
| `pulpcore` | PyPI | All versions to 3.56.0 | None |

Products: Pulpproject Pulp.

## How do I fix CVE-2024-7143?

Apply the vendor's patch.

## Is CVE-2024-7143 being exploited?

There is no known exploitation of CVE-2024-7143 in the wild and no public exploit code.

## Other vulnerabilities in Red Hat Ansible Automation Platform 2

- [CVE-2015-5263](https://insights.sbomify.com/CVE-2015-5263/): Security feature bypass in n/a (high 8.1)
- [CVE-2016-3112](https://insights.sbomify.com/CVE-2016-3112/): Information disclosure in n/a (high 7.5)
- [CVE-2013-7450](https://insights.sbomify.com/CVE-2013-7450/): Hardcoded credentials in n/a (high 7.5)
- [CVE-2016-3108](https://insights.sbomify.com/CVE-2016-3108/): Path traversal in n/a (high 7.1)
- [CVE-2018-10917](https://insights.sbomify.com/CVE-2018-10917/): Path traversal in pulp (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-7143 and fix it if it is affected.

What it is: CVE-2024-7143 is a medium-severity missing authorization vulnerability in Red Hat Ansible Automation Platform 2, published on 7 Aug 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-7143 in the wild and no public exploit code.

Affected packages and fixed versions:
- pulpcore (PyPI): affected all versions up to 3.56.0; no fix listed
- pulpcore (PyPI): affected all versions up to 3.56.0; no fix listed
- pulpcore (PyPI): affected all versions up to 3.56.0; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-7143/ (Markdown: https://insights.sbomify.com/CVE-2024-7143/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-7143
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-7143
- OSV: https://osv.dev/vulnerability/CVE-2024-7143

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-7143/
Summaries are generated and may contain mistakes; the official description above is the record.