Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Snyk] Security upgrade ansible from 2.0.2.0 to 2.9.6 #732

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

snyk-bot
Copy link

@snyk-bot snyk-bot commented Dec 3, 2021

Snyk has created this PR to fix one or more vulnerable packages in the `pip` dependencies of this project.

Changes included in this PR

  • Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
    • requirements.txt

Vulnerabilities that will be fixed

By pinning:
Severity Priority Score (*) Issue Upgrade Breaking Change Exploit Maturity
medium severity 464/1000
Why? Has a fix available, CVSS 5
Information Exposure
SNYK-PYTHON-ANSIBLE-1062705
ansible:
2.0.2.0 -> 2.9.6
No No Known Exploit
medium severity 464/1000
Why? Has a fix available, CVSS 5
Information Exposure
SNYK-PYTHON-ANSIBLE-1070407
ansible:
2.0.2.0 -> 2.9.6
No No Known Exploit
medium severity 464/1000
Why? Has a fix available, CVSS 5
Information Exposure
SNYK-PYTHON-ANSIBLE-1070408
ansible:
2.0.2.0 -> 2.9.6
No No Known Exploit
medium severity 464/1000
Why? Has a fix available, CVSS 5
Information Exposure
SNYK-PYTHON-ANSIBLE-1070409
ansible:
2.0.2.0 -> 2.9.6
No No Known Exploit
medium severity 464/1000
Why? Has a fix available, CVSS 5
Information Exposure
SNYK-PYTHON-ANSIBLE-1086591
ansible:
2.0.2.0 -> 2.9.6
No No Known Exploit
high severity 604/1000
Why? Has a fix available, CVSS 7.8
Information Exposure
SNYK-PYTHON-ANSIBLE-1087441
ansible:
2.0.2.0 -> 2.9.6
No No Known Exploit
medium severity 465/1000
Why? Has a fix available, CVSS 4.8
Information Exposure
SNYK-PYTHON-ANSIBLE-1297166
ansible:
2.0.2.0 -> 2.9.6
No No Known Exploit
high severity 604/1000
Why? Has a fix available, CVSS 7.8
Arbitrary Code Execution
SNYK-PYTHON-ANSIBLE-1570419
ansible:
2.0.2.0 -> 2.9.6
No No Known Exploit
medium severity 479/1000
Why? Has a fix available, CVSS 5.3
Information Exposure
SNYK-PYTHON-ANSIBLE-1571824
ansible:
2.0.2.0 -> 2.9.6
No No Known Exploit
medium severity 444/1000
Why? Has a fix available, CVSS 4.6
Information Exposure
SNYK-PYTHON-ANSIBLE-174932
ansible:
2.0.2.0 -> 2.9.6
No No Known Exploit
high severity 589/1000
Why? Has a fix available, CVSS 7.5
Improper Key Validation
SNYK-PYTHON-ANSIBLE-40436
ansible:
2.0.2.0 -> 2.9.6
No No Known Exploit
critical severity 669/1000
Why? Has a fix available, CVSS 9.1
Arbitrary Command Execution
SNYK-PYTHON-ANSIBLE-40437
ansible:
2.0.2.0 -> 2.9.6
No No Known Exploit
high severity 726/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 8.1
Arbitrary Command Execution
SNYK-PYTHON-ANSIBLE-40446
ansible:
2.0.2.0 -> 2.9.6
No Proof of Concept
high severity 589/1000
Why? Has a fix available, CVSS 7.5
Information Exposure
SNYK-PYTHON-ANSIBLE-42156
ansible:
2.0.2.0 -> 2.9.6
No No Known Exploit
critical severity 704/1000
Why? Has a fix available, CVSS 9.8
Arbitrary Code Injection
SNYK-PYTHON-ANSIBLE-42165
ansible:
2.0.2.0 -> 2.9.6
No No Known Exploit
medium severity 459/1000
Why? Has a fix available, CVSS 4.9
Improper Input Validation
SNYK-PYTHON-ANSIBLE-455610
ansible:
2.0.2.0 -> 2.9.6
No No Known Exploit
low severity 400/1000
Why? Has a fix available, CVSS 3.5
Information Exposure
SNYK-PYTHON-ANSIBLE-474286
ansible:
2.0.2.0 -> 2.9.6
No No Known Exploit
medium severity 534/1000
Why? Has a fix available, CVSS 6.4
Information Exposure
SNYK-PYTHON-ANSIBLE-535490
ansible:
2.0.2.0 -> 2.9.6
No No Known Exploit
medium severity 534/1000
Why? Has a fix available, CVSS 6.4
Improper Input Validation
SNYK-PYTHON-ANSIBLE-535625
ansible:
2.0.2.0 -> 2.9.6
No No Known Exploit
high severity 579/1000
Why? Has a fix available, CVSS 7.3
Arbitrary Code Execution
SNYK-PYTHON-ANSIBLE-536473
ansible:
2.0.2.0 -> 2.9.6
No No Known Exploit
high severity 579/1000
Why? Has a fix available, CVSS 7.3
Arbitrary Code Injection
SNYK-PYTHON-ANSIBLE-536475
ansible:
2.0.2.0 -> 2.9.6
No No Known Exploit
medium severity 636/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 6.3
Arbitrary File Write via Archive Extraction (Zip Slip)
SNYK-PYTHON-ANSIBLE-559542
ansible:
2.0.2.0 -> 2.9.6
No Proof of Concept
medium severity 464/1000
Why? Has a fix available, CVSS 5
Race Condition
SNYK-PYTHON-ANSIBLE-559860
ansible:
2.0.2.0 -> 2.9.6
No No Known Exploit
high severity 609/1000
Why? Has a fix available, CVSS 7.9
Remote Code Execution (RCE)
SNYK-PYTHON-ANSIBLE-561048
ansible:
2.0.2.0 -> 2.9.6
No No Known Exploit
medium severity 464/1000
Why? Has a fix available, CVSS 5
Race Condition
SNYK-PYTHON-ANSIBLE-569107
ansible:
2.0.2.0 -> 2.9.6
No No Known Exploit
medium severity 489/1000
Why? Has a fix available, CVSS 5.5
Information Exposure
SNYK-PYTHON-ANSIBLE-585821
ansible:
2.0.2.0 -> 2.9.6
No No Known Exploit
medium severity 464/1000
Why? Has a fix available, CVSS 5
Information Exposure
SNYK-PYTHON-ANSIBLE-597661
ansible:
2.0.2.0 -> 2.9.6
No No Known Exploit
high severity 604/1000
Why? Has a fix available, CVSS 7.8
Information Exposure
SNYK-PYTHON-ANSIBLE-72546
ansible:
2.0.2.0 -> 2.9.6
No No Known Exploit
medium severity 479/1000
Why? Has a fix available, CVSS 5.3
Information Exposure
SNYK-PYTHON-ANSIBLE-72650
ansible:
2.0.2.0 -> 2.9.6
No No Known Exploit
low severity 369/1000
Why? Has a fix available, CVSS 3.1
Information Exposure
SNYK-PYTHON-ANSIBLE-72696
ansible:
2.0.2.0 -> 2.9.6
No No Known Exploit

(*) Note that the real score may have changed since the PR was raised.

Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the effected dependencies could be upgraded.

Check the changes in this PR to ensure they won't cause issues with your project.


Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report

🛠 Adjust project settings

📚 Read more about Snyk's upgrade and patch logic

The following vulnerabilities are fixed by pinning transitive dependencies:
- https://snyk.io/vuln/SNYK-PYTHON-ANSIBLE-1062705
- https://snyk.io/vuln/SNYK-PYTHON-ANSIBLE-1070407
- https://snyk.io/vuln/SNYK-PYTHON-ANSIBLE-1070408
- https://snyk.io/vuln/SNYK-PYTHON-ANSIBLE-1070409
- https://snyk.io/vuln/SNYK-PYTHON-ANSIBLE-1086591
- https://snyk.io/vuln/SNYK-PYTHON-ANSIBLE-1087441
- https://snyk.io/vuln/SNYK-PYTHON-ANSIBLE-1297166
- https://snyk.io/vuln/SNYK-PYTHON-ANSIBLE-1570419
- https://snyk.io/vuln/SNYK-PYTHON-ANSIBLE-1571824
- https://snyk.io/vuln/SNYK-PYTHON-ANSIBLE-174932
- https://snyk.io/vuln/SNYK-PYTHON-ANSIBLE-40436
- https://snyk.io/vuln/SNYK-PYTHON-ANSIBLE-40437
- https://snyk.io/vuln/SNYK-PYTHON-ANSIBLE-40446
- https://snyk.io/vuln/SNYK-PYTHON-ANSIBLE-42156
- https://snyk.io/vuln/SNYK-PYTHON-ANSIBLE-42165
- https://snyk.io/vuln/SNYK-PYTHON-ANSIBLE-455610
- https://snyk.io/vuln/SNYK-PYTHON-ANSIBLE-474286
- https://snyk.io/vuln/SNYK-PYTHON-ANSIBLE-535490
- https://snyk.io/vuln/SNYK-PYTHON-ANSIBLE-535625
- https://snyk.io/vuln/SNYK-PYTHON-ANSIBLE-536473
- https://snyk.io/vuln/SNYK-PYTHON-ANSIBLE-536475
- https://snyk.io/vuln/SNYK-PYTHON-ANSIBLE-559542
- https://snyk.io/vuln/SNYK-PYTHON-ANSIBLE-559860
- https://snyk.io/vuln/SNYK-PYTHON-ANSIBLE-561048
- https://snyk.io/vuln/SNYK-PYTHON-ANSIBLE-569107
- https://snyk.io/vuln/SNYK-PYTHON-ANSIBLE-585821
- https://snyk.io/vuln/SNYK-PYTHON-ANSIBLE-597661
- https://snyk.io/vuln/SNYK-PYTHON-ANSIBLE-72546
- https://snyk.io/vuln/SNYK-PYTHON-ANSIBLE-72650
- https://snyk.io/vuln/SNYK-PYTHON-ANSIBLE-72696
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant