Correction of PYSEC-2020-220.yaml. Adding fixed version#245
Open
Correction of PYSEC-2020-220.yaml. Adding fixed version#245
Conversation
Signed-off-by: Chi Tran <actran@amazon.com>
Contributor
Author
|
@oliverchang Apologies for tagging you here. But it seems that this PR was hanging for 3 weeks now so wondering if you can help reviewing and merging the change. TIA |
Member
|
https://access.redhat.com/security/cve/CVE-2020-25635 says:
So it seems like this was actually introduced in 1.0.0 and fixed in 1.2.2? Furthermore, this vulnerability seems to be in the https://github.com/ansible-collections/community.aws/ project, (where version 1.2.1 was created in August 2023) and not the https://pypi.org/project/ansible/ project, where version 1.2.1 was created in July 2013. |
This file contains hidden or 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
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.
According to the maintainers/clarification ansible-collections/community.aws#237 (comment) .
The issue was fixed in version 1.2.1. Hence, I am updating the YAML to add fixed version accordingly.