CVE-2020-25646: no_log=True missing for private key content options #125
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
resmo
approved these changes
Oct 13, 2020
|
@Andersson007 @resmo thanks a lot for reviewing! |
|
backport-1? |
|
@Andersson007 @resmo we're releasing 1.x.y releases from |
|
Is this applicable for Ansible 2.9/8/7? |
|
@Akasurde no, the bugs appeared in ansible/ansible after stable-2.9 has been branched. The first official Ansible release affected is 2.10.0. |
|
Great thanks for the information. |
@felixfontein ok, thanks for the info, please mark this in the release issue description |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
SUMMARY
Fix CVE-2020-25646: several modules were missing
no_log=Trueforprivatekey_content(and similar) options.ISSUE TYPE
COMPONENT NAME
openssl_csr
openssl_privatekey_info
openssl_publickey
openssl_signature
x509_certificate
x509_crl