CVE-2019-14904: A flaw was found in the solaris_zone module from the Ansible Community modules.
Noroxi assessment
Priority: Monitor (action score 29/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.41% (FIRST EPSS).
- Someone with local access to the system can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: ansible (Alpine:v3.10) 2.8.8-r0; ansible (Alpine:v3.11) 2.9.3-r0; ansible-base (Alpine:v3.13) 2.9.3-r0.
Low priority for now. Upgrade to ansible (Alpine:v3.10) 2.8.8-r0; ansible (Alpine:v3.11) 2.9.3-r0; ansible-base (Alpine:v3.13) 2.9.3-r0 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Aug 25, 2020
- Updated
- Jun 16, 2026
- EPSS
- 0.4% · 36th percentile
- CWE
- CWE-20
Report tools
Action score
29
Low priority for now.
- CVSS
- 29 / 40 · 7.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| redhat | ansible | cpe:2.3:a:redhat:ansible |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.
n/a Ansible
- All versions before ansible-engine 2.9.4, before ansible-engine 2.8.8 and before ansible-engine 2.7.16affected
Affected versions · NVD (5)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux10.0
- debian debian linux9.0
- redhat ansiblebefore 2.7.15
- redhat ansible2.8.0 and later · before 2.8.7
- redhat ansible2.9.0 and later · before 2.9.2
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.10 | ansible | from 2.8.0 · before 2.8.8-r0 | 2.8.8-r0 |
| Alpine:v3.11 | ansible | from 2.8.0 · before 2.9.3-r0 | 2.9.3-r0 |
| Alpine:v3.13 | ansible-base | before 2.9.3-r0 | 2.9.3-r0 |
| Alpine:v3.9 | ansible | from 2.8.0 · before 2.7.16-r0 | 2.7.16-r0 |
| Debian:10 | ansible | before 2.7.7+dfsg-1+deb10u1 | 2.7.7+dfsg-1+deb10u1 |
| Debian:12 | ansible | before 2.9.4+dfsg-1 | 2.9.4+dfsg-1 |
| Debian:9 | ansible | before 2.2.1.0-2+deb9u2 | 2.2.1.0-2+deb9u2 |
| openSUSE:Leap 15.1 | ansible | before 2.9.6-lp151.2.7.1 | 2.9.6-lp151.2.7.1 |
| openSUSE:Leap 15.3 | ansible | before 2.9.21-bp153.2.3.1 | 2.9.21-bp153.2.3.1 |
| PyPI | ansible | from 2.8.0 · before 2.8.7 | 2.8.7 |
| PyPI | ansible | from 2.8.0a1 · before 2.8.8 | 2.8.8 |
| PyPI | ansible | from 2.9.0 · before 2.9.2 | 2.9.2 |
| PyPI | ansible | from 2.9.0a1 · before 2.9.3 | 2.9.3 |
| PyPI | ansible | before 2.7.16 | 2.7.16 |
| PyPI | ansible | before 2.7.15 | 2.7.15 |
| Red Hat:ansible_engine:2.7::el7 | ansible | before 0:2.7.16-1.el7ae | 0:2.7.16-1.el7ae |
| Red Hat:ansible_engine:2.8::el7 | ansible | before 0:2.8.8-1.el7ae | 0:2.8.8-1.el7ae |
| Red Hat:ansible_engine:2.8::el8 | ansible | before 0:2.8.8-1.el8ae | 0:2.8.8-1.el8ae |
| Red Hat:ansible_engine:2.9::el7 | ansible | before 0:2.9.4-1.el7ae | 0:2.9.4-1.el7ae |
| Red Hat:ansible_engine:2.9::el7 | ansible-test | before 0:2.9.4-1.el7ae | 0:2.9.4-1.el7ae |
| Red Hat:ansible_engine:2.9::el8 | ansible | before 0:2.9.4-1.el8ae | 0:2.9.4-1.el8ae |
| Red Hat:ansible_engine:2.9::el8 | ansible-test | before 0:2.9.4-1.el8ae | 0:2.9.4-1.el8ae |
| SUSE:Package Hub 15 SP1 | ansible | before 2.9.6-bp151.3.6.1 | 2.9.6-bp151.3.6.1 |
| SUSE:Package Hub 15 SP3 | ansible | before 2.9.21-bp153.2.3.1 | 2.9.21-bp153.2.3.1 |
Same product
redhat: all recordsOther highest-scoring records for the same primary product.
- CVE-2014-4678The safe_eval function in Ansible before 1.6.4 does not properly restrict the code subset, which allows remote attackers to execute…41Plan
- CVE-2014-4657The safe_eval function in Ansible before 1.5.4 does not properly restrict the code subset, which allows remote attackers to execute…40Plan
- CVE-2014-4967Multiple argument injection vulnerabilities in Ansible before 1.6.7 allow remote attackers to execute arbitrary code by leveraging access…40Plan
Published before and after this one in the same product
- ← EarlierCVE-2020-10684Mar 24, 2020 · A flaw was found in Ansible Engine, all versions 2.7.x, 2.8.x and 2.9.x prior to 2.7.17, 2.8.9 and 2.9.6 respectively, when using…28Monitor
- ← EarlierCVE-2020-10744May 15, 2020 · An incomplete fix was found for the fix of the flaw CVE-2020-1733 ansible: insecure temporary directory when running become_user from…20Monitor
- Later →CVE-2020-25636Oct 5, 2020 · A flaw was found in Ansible Base when using the aws_ssm connection plugin as there is no namespace separation for file transfers.28Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| alpine:ansible | 2.8.8-r0 · Alpine:v3.10 | Package registry (OSV) |
| alpine:ansible-base | 2.9.3-r0 · Alpine:v3.13 | Package registry (OSV) |
| debian:ansible | 2.9.4+dfsg-1 · Debian:12 | Package registry (OSV) |
| opensuse:ansible | 2.9.21-bp153.2.3.1 · openSUSE:Leap 15.3 | Package registry (OSV) |
| opensuse:ansible | 2.9.6-lp151.2.7.1 · openSUSE:Leap 15.1 | Package registry (OSV) |
| PyPI:ansible | 2.7.15 | Package registry (OSV) |
| PyPI:ansible | 2.7.16 | Package registry (OSV) |
| PyPI:ansible | 2.8.7 | Package registry (OSV) |
| PyPI:ansible | 2.8.8 | Package registry (OSV) |
| PyPI:ansible | 2.9.2 | Package registry (OSV) |
| PyPI:ansible | 2.9.3 | Package registry (OSV) |
| red hat:ansible | 0:2.9.4-1.el7ae · Red Hat:ansible_engine:2.9::el7 | Package registry (OSV) |
| red hat:ansible-test | 0:2.9.4-1.el7ae · Red Hat:ansible_engine:2.9::el7 | Package registry (OSV) |
| suse:ansible | 2.9.21-bp153.2.3.1 · SUSE:Package Hub 15 SP3 | Package registry (OSV) |
| suse:ansible | 2.9.6-bp151.3.6.1 · SUSE:Package Hub 15 SP1 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- Administrator privileges are required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- low · data or configuration can be modified
- Availability
- low · the service can be disrupted
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- High
- Integrity impact
- Low
- Availability impact
- Low
Weakness class (CWE)
CWE-20 · Improper Input ValidationCVSS vector
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:L/A:L
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Server Side Include (SSI) InjectionCAPEC-101likelihood: High · High
- Cross Zone ScriptingCAPEC-104likelihood: Medium · High
- Command Line Execution through SQL InjectionCAPEC-108likelihood: Low · Very High
- Object Relational Mapping InjectionCAPEC-109likelihood: Low · High
- SQL Injection through SOAP Parameter TamperingCAPEC-110likelihood: High · Very High
- Double EncodingCAPEC-120likelihood: Low · Medium
- Subverting Environment Variable ValuesCAPEC-13likelihood: High · Very High
ATT&CK techniques
- Obfuscated Files or InformationT1027
- Masquerading: Invalid Code SignatureT1036.001
- Steal Web Session CookieT1539
- Subvert Trust Controls: Code SigningT1553.002
- Impair Defenses:Impair Command History LoggingT1562.003
- Hijack Execution Flow:Dynamic Linker HijackingT1574.006
- Hijack Execution Flow:Path Interception by PATH Environment VariableT1574.007
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.