CVE-2020-14330: Improper Output Neutralization and Improper Encoding or Escaping of Output for Logs in Ansible

ansible Updated 02 Oct 2025

Summary

09/02/2022
Yes i
Moderate
5.5

CVE-2020-14330: Improper Output Neutralization and Improper Encoding or Escaping of Output for Logs in ansible. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

Ansible is an open-source automation tool that allows users to automate tasks such as configuration management, application deployment, and orchestration. It uses a simple and human-readable language called YAML to define automation tasks. The vulnerability identified as CVE-2020-14330 affects the uri module in Ansible. This module is used to send HTTP or HTTPS requests to a specified URI. The vulnerability exposes sensitive data to content and JSON output, allowing an attacker to access logs or outputs of tasks and potentially compromise data confidentiality.

Vulnerability Detail

The vulnerability arises from an improper output neutralization for logs in Ansible's uri module. When using this module, sensitive data can be exposed in the logs or outputs of performed tasks. This flaw enables an attacker to read keys used in playbooks from other users within the uri module. The impact of this vulnerability is primarily on data confidentiality, as sensitive information can be accessed by unauthorized individuals.

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 specific workaround provided for this vulnerability. However, users can mitigate the risk by ensuring they are using Ansible version 2.10.0 or later.

Conclusion

The vulnerability CVE-2020-14330 in Ansible's uri module exposes sensitive data in logs or outputs of tasks, potentially compromising data confidentiality. It is crucial to upgrade to Ansible version 2.10.0 or later to fix this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for ansible →

Share this vulnerability

FAQ

Ansible is an open-source automation tool used for configuration management, application deployment, and orchestration.

The uri module in Ansible is used to send HTTP or HTTPS requests to a specified URI.

The vulnerability primarily affects data confidentiality, as sensitive information can be exposed in logs or outputs of tasks.

To fix this vulnerability, upgrade to Ansible version 2.10.0 or later.

There is no specific workaround provided, but using Ansible version 2.10.0 or later can mitigate the risk.

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