Galaxy_ng: shell injection in legacy role import via unsanitized git ref names
- 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: total
Summary
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.
Timeline
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- CVE published
- 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
- automation-hub
Version range not reported
- python3.11-galaxy-ng
Version range not reported
- python3.12-galaxy-ng
Version range not reported
- python3x-galaxy-ng
Version range not reported
- python-galaxy-ng
Version range not reported
- galaxy-ngPyPI
through 4.9.2