CVE-2020-14330: Ansible - Improper Output Neutralization for Logs

ansible Updated 02 Oct 2025

Summary

11/09/2020
Yes i
Moderate
5.5

CVE-2020-14330: An Improper Output Neutralization for Logs flaw was found in Ansible when using the uri module, where sensitive data is exposed to content and json output. Affects ansible versions < 2.10.0. Fixed in 2.10.0. How to fix ↓

Also tracked for

The same CVE-2020-14330 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Ansible is an open-source automation tool that allows users to automate IT tasks such as configuration management, application deployment, and orchestration. It uses a declarative language to describe system configurations and relies on modules to perform specific tasks. The 'uri' module in Ansible is used to send HTTP or HTTPS requests to a specified URI. This module is vulnerable to an Improper Output Neutralization for Logs flaw, which exposes sensitive data to content and JSON output.

Vulnerability Detail

The vulnerability in Ansible's 'uri' module allows an attacker to access the logs or outputs of performed tasks and read keys used in playbooks from other users. This can lead to a compromise of data confidentiality. The flaw arises from a lack of proper output neutralization, allowing sensitive information to be exposed in logs and outputs.

How To Fix

Latest published version: 14.5.0 as of 22 Oct 2026

pip install --upgrade "ansible==14.5.0"

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

2.10.0

This is the first release that contains the fix.

pip install --upgrade "ansible==2.10.0"

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no known workaround for this vulnerability. It is essential to upgrade to the fixed version of Ansible to mitigate the risk.

Conclusion

The Improper Output Neutralization for Logs vulnerability in Ansible's 'uri' module exposes sensitive data in logs and outputs. Upgrading to Ansible version 2.10.0 or later is necessary to fix this issue and protect data confidentiality. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for ansible →

Share this vulnerability

FAQ

The vulnerability allows an attacker to access sensitive data exposed in logs and outputs, compromising data confidentiality.

You can use the Vulert playground at Vulert Scanner to check if your Ansible installation is affected by this vulnerability. Simply provide your Pipfile.lock for analysis.

No, there is no known workaround. Upgrading to the fixed version of Ansible is the recommended solution.

Yes, this vulnerability can be exploited remotely if an attacker can send malicious requests to the vulnerable 'uri' module.

There are no known instances of this vulnerability being exploited in the wild. However, it is crucial to apply the fix to prevent potential attacks.

Related vulnerabilities

Recent vulnerabilities recorded for ansible.

How To Fix

Latest published version: 14.5.0 as of 22 Oct 2026

pip install --upgrade "ansible==14.5.0"

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

2.10.0

This is the first release that contains the fix.

pip install --upgrade "ansible==2.10.0"

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback