CVE-2020-25646

A flaw was found in Ansible Collection community.crypto. openssl_privatekey_info exposes private key in logs. This directly impacts confidentiality

The product does not neutralize or incorrectly neutralizes output that is written to logs.

Name	Vendor	Start Version	End Version
Community.crypto	Ansible_collections_project	- (including)	- (including)
Ansible	Ubuntu	bionic	*
Ansible	Ubuntu	groovy	*
Ansible	Ubuntu	hirsute	*
Ansible	Ubuntu	impish	*
Ansible	Ubuntu	kinetic	*
Ansible	Ubuntu	lunar	*
Ansible	Ubuntu	mantic	*
Ansible	Ubuntu	trusty	*
Ansible	Ubuntu	trusty/esm	*
Ansible	Ubuntu	xenial	*

This can allow an attacker to forge log entries or inject malicious content into logs. Log forging vulnerabilities occur when:

Assume all input is malicious. Use an “accept known good” input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, “boat” may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as “red” or “blue.”
Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code’s environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.

NVD	https://nvd.nist.gov/vuln/detail/CVE-2020-25646
CWE	https://cwe.mitre.org/data/definitions/117.html

Improper Output Neutralization for Logs