[Snyk] Fix for 38 vulnerabilities #26
Open
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.
Snyk has created this PR to fix one or more vulnerable packages in the `pip` dependencies of this project.
Changes included in this PR
Vulnerabilities that will be fixed
By pinning: 8000 h5>
Severity
Priority Score (*)
Issue
Upgrade
Breaking Change
Exploit Maturity

464/1000
Information Exposure
No
No Known Exploit

464/1000
Information Exposure
No
No Known Exploit

464/1000
Information Exposure
No
No Known Exploit

464/1000
Information Exposure
No
No Known Exploit

464/1000
Information Exposure
No
No Known Exploit

604/1000
Information Exposure
No
No Known Exploit

465/1000
Information Exposure
No
No Known Exploit

656/1000
Command Injection
No
Proof of Concept

604/1000
Arbitrary Code Execution
No
No Known Exploit

479/1000
Information Exposure
No
No Known Exploit

444/1000
Information Exposure
No
No Known Exploit

604/1000
Arbitrary Code Execution
No
No Known Exploit

479/1000
Information Exposure
No
No Known Exploit

669/1000
Arbitrary Command Execution
No
No Known Exploit

726/1000
Arbitrary Command Execution
No
Proof of Concept

614/1000
Arbitrary Code Execution
No
No Known Exploit

589/1000
Information Exposure
No
No Known Exploit

704/1000
Arbitrary Code Injection
No
No Known Exploit

459/1000
Improper Input Validation
No
No Known Exploit

400/1000
Information Exposure
No
No Known Exploit

534/1000
Information Exposure
No
No Known Exploit

534/1000
Improper Input Validation
No
No Known Exploit

579/1000
Arbitrary Code Execution
No
No Known Exploit

579/1000
Arbitrary Code Injection
No
No Known Exploit

636/1000
Arbitrary File Write via Archive Extraction (Zip Slip)
No
Proof of Concept

464/1000
Race Condition
No
No Known Exploit

609/1000
Remote Code Execution (RCE)
No
No Known Exploit

464/1000
Race Condition
No
No Known Exploit

489/1000
Information Exposure
No
No Known Exploit

464/1000
Information Exposure
No
No Known Exploit

604/1000
Information Exposure
No
No Known Exploit

479/1000
Information Exposure
No
No Known Exploit

369/1000
Information Exposure
No
No Known Exploit

696/1000
Regular Expression Denial of Service (ReDoS)
No
Proof of Concept

589/1000
Denial of Service (DoS)
No
No Known Exploit

704/1000
Arbitrary Code Execution
No
No Known Exploit

704/1000
Arbitrary Code Execution
No
No Known Exploit

876/1000
Arbitrary Code Execution
No
Mature
Why? Has a fix available, CVSS 5
SNYK-PYTHON-ANSIBLE-1062705
ansible:
1.9.6 -> 2.9.27
Why? Has a fix available, CVSS 5
SNYK-PYTHON-ANSIBLE-1070407
ansible:
1.9.6 -> 2.9.27
Why? Has a fix available, CVSS 5
SNYK-PYTHON-ANSIBLE-1070408
ansible:
1.9.6 -> 2.9.27
Why? Has a fix available, CVSS 5
SNYK-PYTHON-ANSIBLE-1070409
ansible:
1.9.6 -> 2.9.27
Why? Has a fix available, CVSS 5
SNYK-PYTHON-ANSIBLE-1086591
ansible:
1.9.6 -> 2.9.27
Why? Has a fix available, CVSS 7.8
SNYK-PYTHON-ANSIBLE-1087441
ansible:
1.9.6 -> 2.9.27
Why? Has a fix available, CVSS 4.8
SNYK-PYTHON-ANSIBLE-1297166
ansible:
1.9.6 -> 2.9.27
Why? Proof of Concept exploit, Has a fix available, CVSS 6.7
SNYK-PYTHON-ANSIBLE-1300676
ansible:
1.9.6 -> 2.9.27
Why? Has a fix available, CVSS 7.8
SNYK-PYTHON-ANSIBLE-1570419
ansible:
1.9.6 -> 2.9.27
Why? Has a fix available, CVSS 5.3
SNYK-PYTHON-ANSIBLE-1571824
ansible:
1.9.6 -> 2.9.27
Why? Has a fix available, CVSS 4.6
SNYK-PYTHON-ANSIBLE-174932
ansible:
1.9.6 -> 2.9.27
Why? Has a fix available, CVSS 7.8
SNYK-PYTHON-ANSIBLE-2407598
ansible:
1.9.6 -> 2.9.27
Why? Has a fix available, CVSS 5.3
SNYK-PYTHON-ANSIBLE-2426979
ansible:
1.9.6 -> 2.9.27
Why? Has a fix available, CVSS 9.1
SNYK-PYTHON-ANSIBLE-40437
ansible:
1.9.6 -> 2.9.27
Why? Proof of Concept exploit, Has a fix available, CVSS 8.1
SNYK-PYTHON-ANSIBLE-40446
ansible:
1.9.6 -> 2.9.27
Why? Has a fix available, CVSS 8
SNYK-PYTHON-ANSIBLE-40462
ansible:
1.9.6 -> 2.9.27
Why? Has a fix available, CVSS 7.5
SNYK-PYTHON-ANSIBLE-42156
ansible:
1.9.6 -> 2.9.27
Why? Has a fix available, CVSS 9.8
SNYK-PYTHON-ANSIBLE-42165
ansible:
1.9.6 -> 2.9.27
Why? Has a fix available, CVSS 4.9
SNYK-PYTHON-ANSIBLE-455610
ansible:
1.9.6 -> 2.9.27
Why? Has a fix available, CVSS 3.5
SNYK-PYTHON-ANSIBLE-474286
ansible:
1.9.6 -> 2.9.27
Why? Has a fix available, CVSS 6.4
SNYK-PYTHON-ANSIBLE-535490
ansible:
1.9.6 -> 2.9.27
Why? Has a fix available, CVSS 6.4
SNYK-PYTHON-ANSIBLE-535625
ansible:
1.9.6 -> 2.9.27
Why? Has a fix available, CVSS 7.3
SNYK-PYTHON-ANSIBLE-536473
ansible:
1.9.6 -> 2.9.27
Why? Has a fix available, CVSS 7.3
SNYK-PYTHON-ANSIBLE-536475
ansible:
1.9.6 -> 2.9.27
Why? Proof of Concept exploit, Has a fix available, CVSS 6.3
SNYK-PYTHON-ANSIBLE-559542
ansible:
1.9.6 -> 2.9.27
Why? Has a fix available, CVSS 5
SNYK-PYTHON-ANSIBLE-559860
ansible:
1.9.6 -> 2.9.27
Why? Has a fix available, CVSS 7.9
SNYK-PYTHON-ANSIBLE-561048
ansible:
1.9.6 -> 2.9.27
Why? Has a fix available, CVSS 5
SNYK-PYTHON-ANSIBLE-569107
ansible:
1.9.6 -> 2.9.27
Why? Has a fix available, CVSS 5.5
SNYK-PYTHON-ANSIBLE-585821
ansible:
1.9.6 -> 2.9.27
Why? Has a fix available, CVSS 5
SNYK-PYTHON-ANSIBLE-597661
ansible:
1.9.6 -> 2.9.27
Why? Has a fix available, CVSS 7.8
SNYK-PYTHON-ANSIBLE-72546
ansible:
1.9.6 -> 2.9.27
Why? Has a fix available, CVSS 5.3
SNYK-PYTHON-ANSIBLE-72650
ansible:
1.9.6 -> 2.9.27
Why? Has a fix available, CVSS 3.1
SNYK-PYTHON-ANSIBLE-72696
ansible:
1.9.6 -> 2.9.27
Why? Proof of Concept exploit, Has a fix available, CVSS 7.5
SNYK-PYTHON-PYGMENTS-1086606
pygments:
2.5.2 -> 2.7.4
Why? Has a fix available, CVSS 7.5
SNYK-PYTHON-PYGMENTS-1088505
pygments:
2.5.2 -> 2.7.4
Why? Has a fix available, CVSS 9.8
SNYK-PYTHON-PYYAML-42159
pyyaml:
3.11 -> 5.4
Why? Has a fix available, CVSS 9.8
SNYK-PYTHON-PYYAML-559098
pyyaml:
3.11 -> 5.4
Why? Mature exploit, Has a fix available, CVSS 9.8
SNYK-PYTHON-PYYAML-590151
pyyaml:
3.11 -> 5.4
(*) 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
Learn how to fix vulnerabilities with free interactive lessons:
🦉 Arbitrary Code Execution
🦉 Arbitrary Code Execution
🦉 Arbitrary Code Injection
🦉 More lessons are available in Snyk Learn