Pulp-ansible: bearer tokens are reused across remotes in a worker
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
A flaw was found in pulp-ansible's bearer-token refresh for collection remotes. The access token is kept in one module-level variable and reused for every token download in that worker. A user who can sync an Ansible remote that uses token refresh, and can point that remote at a server they control, receives an access token obtained for a different remote, and can reuse it at the service that issued it. Content stored in Pulp is not changed, and the service is not stopped.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- ansible-automation-platform-24/hub-rhel8
Version range not reported
- ansible-automation-platform-25/hub-rhel8
Version range not reported
- ansible-automation-platform-26/hub-rhel9
Version range not reported
- ansible-automation-platform-27/hub-rhel9
Version range not reported
- python3.11-pulp-ansible
Version range not reported
- python3.12-pulp-ansible
Version range not reported
- python3x-pulp-ansible
Version range not reported
- python-pulp-ansible
Version range not reported
- python3.12-pulp-ansible
Version range not reported
- python-pulp-ansible
Version range not reported