Name | CVE-2019-14858 |
Description | A vulnerability was found in Ansible engine 2.x up to 2.8 and Ansible tower 3.x up to 3.5. When a module has an argument_spec with sub parameters marked as no_log, passing an invalid parameter name to the module will cause the task to fail before the no_log options in the sub parameters are processed. As a result, data in the sub parameter fields will not be masked and will be displayed if Ansible is run with increased verbosity and present in the module invocation arguments for the task. |
Source | CVE (at NVD; CERT, LWN, oss-sec, fulldisc, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more) |
Debian Bugs | 942332 |
The table below lists information on source packages.
Source Package | Release | Version | Status |
---|---|---|---|
ansible (PTS) | jessie, jessie (lts) | 1.7.2+dfsg-2+deb8u3 | fixed |
stretch (security), stretch (lts), stretch | 2.2.1.0-2+deb9u3 | fixed | |
buster (security), buster, buster (lts) | 2.7.7+dfsg-1+deb10u2 | vulnerable | |
bullseye | 2.10.7+merged+base+2.10.17+dfsg-0+deb11u1 | fixed | |
bookworm | 7.7.0+dfsg-3+deb12u1 | fixed | |
sid, trixie | 10.6.0+dfsg-1 | fixed |
The information below is based on the following data on fixed versions.
Package | Type | Release | Fixed Version | Urgency | Origin | Debian Bugs |
---|---|---|---|---|---|---|
ansible | source | jessie | (not affected) | |||
ansible | source | stretch | (not affected) | |||
ansible | source | (unstable) | 2.8.6+dfsg-1 | 942332 |
[buster] - ansible <no-dsa> (Minor issue)
[stretch] - ansible <not-affected> (Vulnerable code was introduced later)
[jessie] - ansible <not-affected> (Vulnerable code introduced later)
https://bugzilla.redhat.com/show_bug.cgi?id=1760593
https://github.com/ansible/ansible/pull/63405
Sub-options/sub-specs/sub-parameters introduced in https://github.com/ansible/ansible/commit/25de905c6e05bd6df91f4299628ee6d386d3da50 (2.4)
Fixed by: https://github.com/ansible/ansible/commit/3dfb8e81bb5f776a6b00c7a90dd087e85b71f8bb (v2.8.6)
Fixed by: https://github.com/ansible/ansible/commit/0fd656e9964a91f2e8b1e9bbf78c74661ab9d37b (v2.7.14)