Improper Output Neutralization for Logs Affecting ansible package, versions <0:2.6.20-1.el7ae


Severity

Recommended
high

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.08% (36th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Improper Output Neutralization for Logs vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-RHEL7-ANSIBLE-5354441
  • published26 Mar 2023
  • disclosed11 Oct 2019

Introduced: 11 Oct 2019

CVE-2019-14858  (opens in a new tab)
CWE-117  (opens in a new tab)
CWE-532  (opens in a new tab)

How to fix?

Upgrade RHEL:7 ansible to version 0:2.6.20-1.el7ae or higher.
This issue was patched in RHSA-2019:3201.

NVD Description

Note: Versions mentioned in the description apply only to the upstream ansible package and not the ansible package as distributed by RHEL. See How to fix? for RHEL:7 relevant fixed versions and status.

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.

CVSS Scores

version 3.1