CVE-2019-14904 json
OS Command Injection and Improper Input Validation in ansible
published 6y ago modified 4mo ago also GHSA-gwr8-5j83-483c , PYSEC-2020-161 , EUVD-2020-0008
- cvss
- 7.3
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 36%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- pypi ansible 2.7.15, 2.7.16, 2.8.7, 2.8.8, 2.9.2, 2.9.3
- redhat ansible 2.7.15, 2.8.7, 2.9.2
- ansible Debian 14, Debian 13, Debian 12 2.9.4+dfsg-1
debian advisories DEBIAN-CVE-2019-14904
- ansible Ubuntu Pro 16.04 LTS 2.0.0.2-2ubuntu1.3+esm5
- ansible Ubuntu Pro 18.04 LTS 2.5.1+dfsg-1ubuntu0.1+esm5
ubuntu advisories UBUNTU-CVE-2019-14904
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- ansible ansible engine 2.9, ansible engine 2 2.9.4-1.el7ae
- ansible ansible engine 2.9, ansible engine 2 2.9.4-1.el8ae
- ansible-test ansible engine 2.9, ansible engine 2 2.9.4-1.el7ae
- ansible-test ansible engine 2.9, ansible engine 2 2.9.4-1.el8ae
- ansible ansible engine 2.8 2.8.8-1.el7ae
- ansible ansible engine 2.8 2.8.8-1.el8ae
- ansible ansible engine 2.7 2.7.16-1.el7ae
red hat advisories RHSA-2020:0218RHSA-2020:0215RHSA-2020:0216RHSA-2020:0217
- storm OpenStack Cloud Crowbar 8, OpenStack Cloud 8, HPE Helion OpenStack 8 1.2.3-3.6.1
- ansible OpenStack Cloud Crowbar 8, OpenStack Cloud 8, HPE Helion OpenStack 8 2.9.14-3.15.1
- grafana OpenStack Cloud Crowbar 8, OpenStack Cloud 8, HPE Helion OpenStack 8 6.7.4-4.12.1
- ardana-mq OpenStack Cloud 8, HPE Helion OpenStack 8 8.0+git.1593618123.678c32b-3.26.1
- ardana-nova OpenStack Cloud 8, HPE Helion OpenStack 8 8.0+git.1601298847.dd01585-3.42.1
- crowbar-core OpenStack Cloud Crowbar 8 5.0+git.1600432272.b3ad722f0-3.44.1
- python-kombu OpenStack Cloud Crowbar 8, OpenStack Cloud 8, HPE Helion OpenStack 8 4.1.0-3.7.1
- ardana-cinder OpenStack Cloud 8, HPE Helion OpenStack 8 8.0+git.1596129856.263f430-3.43.1
suse advisories SUSE-SU-2020:3309-1
- ansible-14 openSUSE Tumbleweed 14.6.0-1.1
- ansible-13 openSUSE Tumbleweed 13.7.0-1.1
- ansible-12 openSUSE Tumbleweed 12.2.0-1.1
- ansible-11 openSUSE Tumbleweed 11.11.0-1.1
- ansible-10 openSUSE Tumbleweed 10.6.0-1.1
- ansible-9 openSUSE Tumbleweed 9.8.0-1.1
- ansible Package Hub 15 SP3, openSUSE Leap 15.3 2.9.21-bp153.2.3.1
- ansible Package Hub 15 SP1 2.9.6-bp151.3.6.1
opensuse advisories openSUSE-SU-2026:12447-1openSUSE-SU-2026:10944-1openSUSE-SU-2025:15753-1openSUSE-SU-2025:15605-1openSUSE-SU-2024:14536-1openSUSE-SU-2024:14244-1
- ansible Alpine 3.10 2.8.8-r0
- ansible Alpine 3.12, Alpine 3.11 2.9.3-r0
- ansible Alpine 3.9 2.7.16-r0
- ansible-base Alpine 3.15, Alpine 3.14, Alpine 3.13 2.9.3-r0
alpine advisories ALPINE-CVE-2019-14904
Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- github.com/ansible/ansible@589a415 commit
- github.com/ansible/ansible@6a86650 commit
- github.com/ansible/ansible@a1b0f72 commit
- github.com/ansible/ansible#65686 pull request
Is CVE-2019-14904 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2019-14904 updated cvss 7.3
Ansible: vulnerability in solaris_zone module via crafted solaris zone
-
Red Hat Ansible Tower 3 ansibleaffected: workaround, no fix available “Currently, there is no mitigation for this issue.”
-
Red Hat Ceph Storage 2 ansible Red Hat Ceph Storage 3 ansible Red Hat OpenStack Platform 10 (Newton) ansible Red Hat OpenStack Platform 13 (Queens) ansible Red Hat OpenStack Platform 14 (Rocky) ansible Red Hat Storage 3 ansibleaffected: workaround, no fix planned “Currently, there is no mitigation for this issue.”
-
Red Hat Ansible Engine 2 for RHEL 7 ansible 2.9.4-1.el7ae, ansible-test 2.9.4-1.el7ae Red Hat Ansible Engine 2 for RHEL 8 ansible 2.9.4-1.el8ae, ansible-test 2.9.4-1.el8aefixed: vendor fix “Currently, there is no mitigation for this issue.” RHSA-2020:0218
-
Red Hat Ansible Engine 2.7 for RHEL 7 Server ansible 2.7.16-1.el7aefixed: vendor fix “Currently, there is no mitigation for this issue.” RHSA-2020:0217
-
Red Hat Ansible Engine 2.8 for RHEL 7 Server ansible 2.8.8-1.el7ae Red Hat Ansible Engine 2.8 for RHEL 8 ansible 2.8.8-1.el8aefixed: vendor fix “Currently, there is no mitigation for this issue.” RHSA-2020:0216
-
Red Hat Ansible Engine 2.9 for RHEL 7 Server ansible 2.9.4-1.el7ae, ansible-test 2.9.4-1.el7ae Red Hat Ansible Engine 2.9 for RHEL 8 ansible 2.9.4-1.el8ae, ansible-test 2.9.4-1.el8aefixed: vendor fix “Currently, there is no mitigation for this issue.” RHSA-2020:0215
-
Red Hat CloudForms Management Engine 5 ansiblenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.42% chance of exploitation in the next 30 days, higher than 36% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.3 | CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:L/A:L |
| NVD | 2.0 | 6.1 | AV:L/AC:L/Au:N/C:C/I:P/A:P |
| GitHub | 3.1 | 7.3 | CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:L/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | ansible | <2.7.16 >=2.8.0a1, <2.8.8 >=2.9.0a1, <2.9.3 <2.7.15 >=2.8.0, <2.8.7 >=2.9.0, <2.9.2 |
2.7.16 2.8.8 2.9.3 2.7.15 2.8.7 2.9.2 |
Affected products
- n/a Ansible
Classification
References
-
github.com
/ansible/ansible/pull/65686
web, patch, third-party-advisory
-
github.com
/ansible/ansible/commit/589a415f887b6f2bb65cd07fe6b2e9d0a8156b69
web
-
github.com
/ansible/ansible/commit/6a86650109b8654f5898369e45d3857624edf907
web
-
github.com
/ansible/ansible/commit/a1b0f72c98b4b2afaab8aafa255e82c2075049c8
web
-
debian.org
/security/2021/dsa-4950
vendor-advisory, web, third-party-advisory
-
bugzilla.redhat.com
/show_bug.cgi?id=1776944
web, issue-tracking, vendor-advisory, report
-
lists.debian.org
/debian-lts-announce/2021/01/msg00023.html
mailing-list, web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2019-14904
advisory
-
github.com
/advisories/GHSA-gwr8-5j83-483c
advisory
-
github.com
/ansible/ansible
package
-
github.com
/pypa/advisory-database/tree/main/vulns/ansible/PYSEC-2020-161.yaml
web
Sources
- CVE List CVE-2019-14904
- GitHub Advisory GHSA-gwr8-5j83-483c
- NVD CVE-2019-14904
- OSV PYSEC-2020-161
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.