GHSA-gwr8-5j83-483c is a high-severity (CVSS 7.3) Improper Input Validation vulnerability in ansible. O3 Security confirms whether GHSA-gwr8-5j83-483c is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
OS Command Injection and Improper Input Validation in ansible
Real-World Exposure
ansible🐍ansible🐍ansibleReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
A flaw was found in the solaris_zone module from the Ansible Community modules. When setting the name for the zone on the Solaris host, the zone name is checked by listing the process with the 'ps' bare command on the remote machine. An attacker could take advantage of this flaw by crafting the name of the zone and executing arbitrary commands in the remote host. Ansible Engine 2.7.15, 2.8.7, and 2.9.2 as well as previous versions are affected.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | ansible | all versions | 2.7.16 |
| 🐍PyPI | ansible | ≥ 2.8.0a1&&< 2.8.8 | 2.8.8 |
| 🐍PyPI | ansible | ≥ 2.9.0a1&&< 2.9.3 | 2.9.3 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ansible. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update ansible to 2.7.16 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gwr8-5j83-483c 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.
How O3 protects you
O3 pinpoints whether GHSA-gwr8-5j83-483c is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-gwr8-5j83-483c. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
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.
Because a flaw exploit would depend on the use of Solaris and Red Hat does not support RHOSP on Solaris, the RHOSP Ansible package will not be updated at this time. Ansible Engine 2.7.15, 2.8.7, and 2.9.2 as well as previous versions are affected.
Frequently Asked Questions
Is GHSA-gwr8-5j83-483c in your dependencies?
O3 detects GHSA-gwr8-5j83-483c across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.