OpenShift Assisted Installer leaks image pull secrets as plaintext in installation logsGHSA-g8xm-p2h4-v6jp
MEDIUMFix: openshift/assisted-installer@2403dadGHSA-g8xm-p2h4-v6jp is a medium-severity (CVSS 5.5) CWE-532 vulnerability in github.com/openshift/assisted-installer. A fix is available for github.com/openshift/assisted-installer — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-g8xm-p2h4-v6jp.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/openshift/assisted-installerReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
A vulnerability was found in OpenShift Assisted Installer. During generation of the Discovery ISO, image pull secrets were leaked as plaintext in the installation logs. An authenticated user could exploit this by re-using the image pull secret to pull container images from the registry as the associated user.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/openshift/assisted-installer | all versions | 1.0.25.1go get github.com/openshift/assisted-installer@v1.0.25.1 |
Affected Products
openshift assisted installerredhatopenshift container platformredhatDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/openshift/assisted-installer, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/openshift/assisted-installer to 1.0.25.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g8xm-p2h4-v6jp is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
| Product | Fixed in | Advisory |
|---|---|---|
| RHAI-1.0-RHEL-8 | rhai-tech-preview/assisted-installer-reporter-rhel8:v1.0.0-101 | RHEA-2021:3455 |
Frequently Asked Questions
Is GHSA-g8xm-p2h4-v6jp in your dependencies?
Find it across Go, including transitive dependencies.