Bug 1640642 (CVE-2018-16837) - CVE-2018-16837 Ansible: Information leak in "user" module
Summary: CVE-2018-16837 Ansible: Information leak in "user" module
Status: CLOSED ERRATA
Alias: CVE-2018-16837
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard: impact=moderate,public=20181023:0646,...
Keywords: Security
Depends On: 1644841 1644843 1644844 1644845
Blocks: 1640345
TreeView+ depends on / blocked
 
Reported: 2018-10-18 13:14 UTC by Borja Tarraso
Modified: 2019-06-08 23:40 UTC (History)
9 users (show)

(edit)
The User module in Ansible leaks any data which is passed on as a parameter to ssh-keygen. This could lead to undesirable situations such as passphrase credentials being passed as a parameter for the ssh-keygen executable, showing those credentials in clear text form for every user which have access just to the process list.
Clone Of:
(edit)
Last Closed: 2018-11-05 12:22:12 UTC


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2018:3460 None None None 2018-11-05 10:54 UTC
Red Hat Product Errata RHSA-2018:3461 None None None 2018-11-05 10:55 UTC
Red Hat Product Errata RHSA-2018:3462 None None None 2018-11-05 10:55 UTC
Red Hat Product Errata RHSA-2018:3463 None None None 2018-11-05 10:55 UTC

Description Borja Tarraso 2018-10-18 13:14:22 UTC
"User" module leaks any data which is passed on as a parameter to ssh-keygen. This could lean in undesirable situations such as passphrases credentials passed as a parameter for the ssh-keygen executable. Showing those credentials in clear text form for every user which have access just to the process list.

Comment 1 Borja Tarraso 2018-10-18 13:14:26 UTC
Acknowledgments:

Name: Markus Teufelberger (mgIT Consulting)

Comment 4 Salvatore Bonaccorso 2018-10-24 18:52:02 UTC
Is there any more information on e.g. upstream fix for this issue? Upstream issue reference?

Comment 5 Borja Tarraso 2018-10-25 08:33:12 UTC
In reply to comment 4:
> Is there any more information on e.g. upstream fix for this issue? Upstream
> issue reference?

Here it is: https://github.com/ansible/ansible/pull/47436

Comment 6 Borja Tarraso 2018-10-25 10:16:28 UTC
External References:

https://github.com/ansible/ansible/pull/47436

Comment 7 Chad Scribner 2018-10-30 16:15:31 UTC
Hi Borja,

Are there any blockers to getting https://github.com/ansible/ansible/pull/47487 merged in?  I have a customer interested to know when they can expected the fixes for 2.5, 2.6, and 2.7 to be released via errata.

Comment 9 Borja Tarraso 2018-10-31 17:17:07 UTC
In reply to comment 7:
> Hi Borja,
> 
> Are there any blockers to getting
> https://github.com/ansible/ansible/pull/47487 merged in?  I have a customer
> interested to know when they can expected the fixes for 2.5, 2.6, and 2.7 to
> be released via errata.

We expect to have it by today the fix for all versions, depends of how stable are the tests if I am not wrong. For 2.7 it has been already fixed. Erratas should be soon there.

Comment 10 errata-xmlrpc 2018-11-05 10:54:26 UTC
This issue has been addressed in the following products:

  Red Hat Ansible Engine 2.6 for RHEL 7

Via RHSA-2018:3460 https://access.redhat.com/errata/RHSA-2018:3460

Comment 11 errata-xmlrpc 2018-11-05 10:55:01 UTC
This issue has been addressed in the following products:

  Red Hat Ansible Engine 2.7 for RHEL 7

Via RHSA-2018:3463 https://access.redhat.com/errata/RHSA-2018:3463

Comment 12 errata-xmlrpc 2018-11-05 10:55:15 UTC
This issue has been addressed in the following products:

  Red Hat Ansible Engine 2.5 for RHEL 7

Via RHSA-2018:3461 https://access.redhat.com/errata/RHSA-2018:3461

Comment 13 errata-xmlrpc 2018-11-05 10:55:24 UTC
This issue has been addressed in the following products:

  Red Hat Ansible Engine 2 for RHEL 7

Via RHSA-2018:3462 https://access.redhat.com/errata/RHSA-2018:3462

Comment 14 Borja Tarraso 2018-11-05 12:22:12 UTC
Closing the flaw; affects are resolved and trackers also are closed.


Note You need to log in before you can comment on or make changes to this bug.