Pulp-container: registry credentials are reused across remotes in a worker
Red Hat Ansible Automation Platform 2 · Red Hat Satellite 6 · Red Hat Update Infrastructure 4 for Cloud Providers · Red Hat Update Infrastructure 5
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Red Hat Red Hat Ansible Automation Platform 2 | — | No fix yet |
| Red Hat Red Hat Ansible Automation Platform 2 | — | No fix yet |
| Red Hat Red Hat Ansible Automation Platform 2 | — | No fix yet |
| Red Hat Red Hat Ansible Automation Platform 2 | — | No fix yet |
| Red Hat Red Hat Ansible Automation Platform 2 | — | No fix yet |
| Red Hat Red Hat Ansible Automation Platform 2 | — | No fix yet |
| Red Hat Red Hat Ansible Automation Platform 2 | — | No fix yet |
| Red Hat Red Hat Ansible Automation Platform 2 | — | No fix yet |
| Red Hat Red Hat Satellite 6 | — | No fix yet |
| Red Hat Red Hat Satellite 6 | — | No fix yet |
| Red Hat Red Hat Update Infrastructure 4 for Cloud Providers | — | No fix yet |
| Red Hat Red Hat Update Infrastructure 4 for Cloud Providers | — | No fix yet |
| Red Hat Red Hat Update Infrastructure 5 | — | No fix yet |
| Red Hat Red Hat Update Infrastructure 5 | — | No fix yet |
| Red Hat Red Hat Update Infrastructure 5 | — | No fix yet |
Original description
A flaw was found in pulp-container when it authenticates to an upstream registry. Basic and bearer credentials from one remote are reused for later downloads in the same worker. A user who can sync a container remote, and can point that remote at a server they control, receives the username, password, or bearer token stored for a different remote, and can reuse that credential at the upstream registry. Content stored in Pulp is not changed, and the service is not stopped.
From the CVE record · redhat