Galaxy_ng: shell injection in legacy role import via unsanitized git ref names
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions |
|---|---|---|---|
| Red Hat | Red Hat Ansible Automation Platform 2 | unaffected | — |
| Red Hat | Red Hat Ansible Automation Platform 2 | affected | — |
| Red Hat | Red Hat Ansible Automation Platform 2 | affected | — |
| Red Hat | Red Hat Ansible Automation Platform 2 | affected | — |
| Red Hat | Red Hat Ansible Automation Platform 2 | affected | — |
| Red Hat | Red Hat Ansible Automation Platform 2 | unknown | — |
| Red Hat | Red Hat Ansible Automation Platform 2 | unknown | — |
| Red Hat | Red Hat Ansible Automation Platform 2 | unknown | — |
| Red Hat | Red Hat Ansible Automation Platform 2 | unknown | — |
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Redhat | Ansible Automation Platform |
|
Vendor Workaround
The following practices would help for avoiding exposure and mitigate this flaw: 1. Ensure that GALAXY_ENABLE_LEGACY_ROLES is set to False (the default) in your Galaxy/Hub configuration. This prevents the v1 API routes from being registered, making the vulnerable endpoint entirely unreachable. 2. If legacy role support must be enabled, restrict access to the Galaxy/Hub API to trusted users only. The vulnerability requires authentication, so limiting who can authenticate reduces exposure. 3. Monitor import activity for suspicious git references containing shell metacharacters in branch or tag names.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-6hw7-j4jw-wpff | Galaxy NG: command injection vulnerability |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.889% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | A command injection vulnerability was found in galaxy_ng. The do_git_checkout() function in the legacy role import API (v1) interpolates unsanitized git ref names (branch/tag names) into shell commands executed via subprocess.run() with shell=True. An authenticated user who controls a git repository can create a branch or tag with shell metacharacters in the name to achieve remote code execution on the pulp worker. The vulnerable endpoint is only reachable when GALAXY_ENABLE_LEGACY_ROLES is set to True, which is not the default configuration. | |
| Title | Galaxy_ng: shell injection in legacy role import via unsanitized git ref names | |
| First Time appeared |
Redhat
Redhat ansible Automation Platform |
|
| Weaknesses | CWE-78 | |
| CPEs | cpe:/a:redhat:ansible_automation_platform:2 | |
| Vendors & Products |
Redhat
Redhat ansible Automation Platform |
|
| References |
| |
| Metrics |
cvssV3_1
|