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] Fix for 24 vulnerabilities #309

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

Conversation

pcic-devops
Copy link

This PR was automatically created by Snyk using the credentials of a real user.


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
requests 2.21.0 has requirement urllib3<1.25,>=1.21.1, but you have urllib3 1.26.18.
Mako 1.1.4 requires MarkupSafe, which is not installed.
Jinja2 3.1.3 requires MarkupSafe, which is not installed.
Flask 1.0.2 requires Werkzeug, which is not installed.

Vulnerabilities that will be fixed

By pinning:
Severity Issue Upgrade Breaking Change Exploit Maturity
critical severity Improper Following of a Certificate's Chain of Trust
SNYK-PYTHON-CERTIFI-5805047
certifi:
2021.5.30 -> 2023.7.22
No No Known Exploit
high severity Improper Certificate Validation
SNYK-PYTHON-CRYPTOGRAPHY-5777683
cryptography:
3.3.2 -> 42.0.2
No Proof of Concept
low severity Insufficient Verification of Data Authenticity
SNYK-PYTHON-CRYPTOGRAPHY-5813745
cryptography:
3.3.2 -> 42.0.2
No No Known Exploit
medium severity Denial of Service (DoS)
SNYK-PYTHON-CRYPTOGRAPHY-5813746
cryptography:
3.3.2 -> 42.0.2
No No Known Exploit
low severity Denial of Service (DoS)
SNYK-PYTHON-CRYPTOGRAPHY-5813750
cryptography:
3.3.2 -> 42.0.2
No No Known Exploit
medium severity Denial of Service (DoS)
SNYK-PYTHON-CRYPTOGRAPHY-5914629
cryptography:
3.3.2 -> 42.0.2
No No Known Exploit
medium severity Missing Cryptographic Step
SNYK-PYTHON-CRYPTOGRAPHY-6036192
cryptography:
3.3.2 -> 42.0.2
No No Known Exploit
medium severity Denial of Service (DoS)
SNYK-PYTHON-CRYPTOGRAPHY-6050294
cryptography:
3.3.2 -> 42.0.2
No No Known Exploit
medium severity NULL Pointer Dereference
SNYK-PYTHON-CRYPTOGRAPHY-6092044
cryptography:
3.3.2 -> 42.0.2
No Proof of Concept
medium severity Information Exposure
SNYK-PYTHON-CRYPTOGRAPHY-6126975
cryptography:
3.3.2 -> 42.0.2
No Proof of Concept
medium severity NULL Pointer Dereference
SNYK-PYTHON-CRYPTOGRAPHY-6210214
cryptography:
3.3.2 -> 42.0.2
No No Known Exploit
critical severity Remote Code Execution (RCE)
SNYK-PYTHON-GITPYTHON-5840584
gitpython:
2.1.15 -> 3.1.41
No Proof of Concept
high severity Untrusted Search Path
SNYK-PYTHON-GITPYTHON-5871282
gitpython:
2.1.15 -> 3.1.41
No Proof of Concept
medium severity Directory Traversal
SNYK-PYTHON-GITPYTHON-5876644
gitpython:
2.1.15 -> 3.1.41
No Proof of Concept
high severity Untrusted Search Path
SNYK-PYTHON-GITPYTHON-6150683
gitpython:
2.1.15 -> 3.1.41
No Proof of Concept
medium severity Cross-site Scripting (XSS)
SNYK-PYTHON-JINJA2-6150717
jinja2:
2.11.3 -> 3.1.3
No No Known Exploit
critical severity Heap-based Buffer Overflow
SNYK-PYTHON-PILLOW-5918878
pillow:
4.3.0 -> 10.2.0
No Mature
high severity Uncontrolled Resource Consumption ('Resource Exhaustion')
SNYK-PYTHON-PILLOW-6043904
pillow:
4.3.0 -> 10.2.0
No No Known Exploit
high severity Eval Injection
SNYK-PYTHON-PILLOW-6182918
pillow:
4.3.0 -> 10.2.0
No Proof of Concept
high severity Denial of Service (DoS)
SNYK-PYTHON-PILLOW-6219984
pillow:
4.3.0 -> 10.2.0
No No Known Exploit
high severity Denial of Service (DoS)
SNYK-PYTHON-PILLOW-6219986
pillow:
4.3.0 -> 10.2.0
No No Known Exploit
medium severity Information Exposure Through Sent Data
SNYK-PYTHON-URLLIB3-5926907
urllib3:
1.26.5 -> 1.26.18
No No Known Exploit
medium severity Information Exposure Through Sent Data
SNYK-PYTHON-URLLIB3-6002459
urllib3:
1.26.5 -> 1.26.18
No No Known Exploit
medium severity Inefficient Algorithmic Complexity
SNYK-PYTHON-WERKZEUG-6035177
werkzeug:
0.15.3 -> 2.3.8
No No Known Exploit

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 affected 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:

🦉 Denial of Service (DoS)
🦉 NULL Pointer Dereference
🦉 Remote Code Execution (RCE)
🦉 More lessons are available in Snyk Learn

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