Skip to content

[Snyk] Fix for 18 vulnerabilities#8

Open
rodtreweek wants to merge 1 commit intomasterfrom
snyk-fix-f68e9a95a391e7398f9915ab55b2f525
Open

[Snyk] Fix for 18 vulnerabilities#8
rodtreweek wants to merge 1 commit intomasterfrom
snyk-fix-f68e9a95a391e7398f9915ab55b2f525

Conversation

@rodtreweek
Copy link
Copy Markdown
Owner

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
⚠️ Warning
azure-cli-core 2.15.1 has requirement azure-mgmt-resource==10.2.0, but you have azure-mgmt-resource 1.2.2.
azure-cli-core 2.15.1 has requirement msrestazure>=0.6.3, but you have msrestazure 0.4.34.

Vulnerabilities that will be fixed

By pinning:
Severity Priority Score (*) Issue Upgrade Breaking Change Exploit Maturity
high severity 589/1000
Why? Has a fix available, CVSS 7.5
Information Exposure
SNYK-PYTHON-ANSIBLE-42156
ansible:
2.4.3.0 -> 2.5.5
No No Known Exploit
low severity 400/1000
Why? Has a fix available, CVSS 3.5
Information Exposure
SNYK-PYTHON-ANSIBLE-474286
ansible:
2.4.3.0 -> 2.5.5
No No Known Exploit
medium severity 534/1000
Why? Has a fix available, CVSS 6.4
Information Exposure
SNYK-PYTHON-ANSIBLE-535490
ansible:
2.4.3.0 -> 2.5.5
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.4.3.0 -> 2.5.5
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.4.3.0 -> 2.5.5
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.4.3.0 -> 2.5.5
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.4.3.0 -> 2.5.5
No Proof of Concept
medium severity 464/1000
Why? Has a fix available, CVSS 5
Race Condition
SNYK-PYTHON-ANSIBLE-559860
ansible:
2.4.3.0 -> 2.5.5
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.4.3.0 -> 2.5.5
No No Known Exploit
medium severity 464/1000
Why? Has a fix available, CVSS 5
Race Condition
SNYK-PYTHON-ANSIBLE-569107
ansible:
2.4.3.0 -> 2.5.5
No No Known Exploit
medium severity 489/1000
Why? Has a fix available, CVSS 5.5
Information Exposure
SNYK-PYTHON-ANSIBLE-585821
ansible:
2.4.3.0 -> 2.5.5
No No Known Exploit
medium severity 464/1000
Why? Has a fix available, CVSS 5
Information Exposure
SNYK-PYTHON-ANSIBLE-597661
ansible:
2.4.3.0 -> 2.5.5
No No Known Exploit
high severity 604/1000
Why? Has a fix available, CVSS 7.8
Information Exposure
SNYK-PYTHON-ANSIBLE-72546
ansible:
2.4.3.0 -> 2.5.5
No No Known Exploit
medium severity 479/1000
Why? Has a fix available, CVSS 5.3
Information Exposure
SNYK-PYTHON-ANSIBLE-72650
ansible:
2.4.3.0 -> 2.5.5
No No Known Exploit
low severity 369/1000
Why? Has a fix available, CVSS 3.1
Information Exposure
SNYK-PYTHON-ANSIBLE-72696
ansible:
2.4.3.0 -> 2.5.5
No No Known Exploit
medium severity 658/1000
Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 5.3
Regular Expression Denial of Service (ReDoS)
SNYK-PYTHON-JINJA2-1012994
jinja2:
2.8 -> 2.11.3
No Proof of Concept
medium severity 514/1000
Why? Has a fix available, CVSS 6
Sandbox Escape
SNYK-PYTHON-JINJA2-174126
jinja2:
2.8 -> 2.11.3
No No Known Exploit
high severity 644/1000
Why? Has a fix available, CVSS 8.6
Sandbox Bypass
SNYK-PYTHON-JINJA2-455616
jinja2:
2.8 -> 2.11.3
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

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.

2 participants