Skip to content
This repository has been archived by the owner on Jul 16, 2024. It is now read-only.

[Snyk] Fix for 15 vulnerabilities #121

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

Conversation

m-ajay
Copy link
Owner

@m-ajay m-ajay commented Feb 17, 2023

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/base.txt
⚠️ Warning
python3-openid 3.2.0 has requirement defusedxml<=0.4.1, but you have defusedxml 0.7.1.
Flask 1.1.4 requires Werkzeug, which is not installed.
Flask-JWT-Extended 3.25.1 requires Werkzeug, which is not installed.
email-validator 1.1.3 requires idna, which is not installed.
deprecation 2.1.0 requires packaging, which is not installed.
bleach 3.3.1 requires packaging, which is not installed.

Vulnerabilities that will be fixed

By pinning:
Severity Priority Score (*) Issue Upgrade Breaking Change Exploit Maturity
medium severity 509/1000
Why? Has a fix available, CVSS 5.9
Denial of Service (DoS)
SNYK-PYTHON-CRYPTOGRAPHY-3172287
cryptography:
3.4.7 -> 39.0.1
No No Known Exploit
medium severity 526/1000
Why? Recently disclosed, Has a fix available, CVSS 4.8
Expected Behavior Violation
SNYK-PYTHON-CRYPTOGRAPHY-3314966
cryptography:
3.4.7 -> 39.0.1
No No Known Exploit
medium severity 581/1000
Why? Recently disclosed, Has a fix available, CVSS 5.9
Use After Free
SNYK-PYTHON-CRYPTOGRAPHY-3315324
cryptography:
3.4.7 -> 39.0.1
No No Known Exploit
high severity 656/1000
Why? Recently disclosed, Has a fix available, CVSS 7.4
Access of Resource Using Incompatible Type ('Type Confusion')
SNYK-PYTHON-CRYPTOGRAPHY-3315328
cryptography:
3.4.7 -> 39.0.1
No No Known Exploit
medium severity 551/1000
Why? Recently disclosed, Has a fix available, CVSS 5.3
Timing Attack
SNYK-PYTHON-CRYPTOGRAPHY-3315331
cryptography:
3.4.7 -> 39.0.1
No No Known Exploit
medium severity 581/1000
Why? Recently disclosed, Has a fix available, CVSS 5.9
Denial of Service (DoS)
SNYK-PYTHON-CRYPTOGRAPHY-3315452
cryptography:
3.4.7 -> 39.0.1
No No Known Exploit
medium severity 628/1000
Why? Currently trending on Twitter, Recently disclosed, Has a fix available, CVSS 5.9
Denial of Service (DoS)
SNYK-PYTHON-CRYPTOGRAPHY-3315972
cryptography:
3.4.7 -> 39.0.1
No No Known Exploit
medium severity 581/1000
Why? Recently disclosed, Has a fix available, CVSS 5.9
Denial of Service (DoS)
SNYK-PYTHON-CRYPTOGRAPHY-3315975
cryptography:
3.4.7 -> 39.0.1
No No Known Exploit
medium severity 581/1000
Why? Recently disclosed, Has a fix available, CVSS 5.9
Denial of Service (DoS)
SNYK-PYTHON-CRYPTOGRAPHY-3316038
cryptography:
3.4.7 -> 39.0.1
No No Known Exploit
high severity 661/1000
Why? Recently disclosed, Has a fix available, CVSS 7.5
Denial of Service (DoS)
SNYK-PYTHON-CRYPTOGRAPHY-3316211
cryptography:
3.4.7 -> 39.0.1
No No Known Exploit
low severity 506/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 3.7
NULL Pointer Dereference
SNYK-PYTHON-NUMPY-2321964
numpy:
1.21.1 -> 1.22.2
No Proof of Concept
low severity 399/1000
Why? Has a fix available, CVSS 3.7
Buffer Overflow
SNYK-PYTHON-NUMPY-2321966
numpy:
1.21.1 -> 1.22.2
No No Known Exploit
low severity 506/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 3.7
Denial of Service (DoS)
SNYK-PYTHON-NUMPY-2321970
numpy:
1.21.1 -> 1.22.2
No Proof of Concept
low severity 416/1000
Why? Recently disclosed, Has a fix available, CVSS 2.6
Access Restriction Bypass
SNYK-PYTHON-WERKZEUG-3319935
werkzeug:
1.0.1 -> 2.2.3
No No Known Exploit
high severity 661/1000
Why? Recently disclosed, Has a fix available, CVSS 7.5
Denial of Service (DoS)
SNYK-PYTHON-WERKZEUG-3319936
werkzeug:
1.0.1 -> 2.2.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 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)
🦉 Denial of Service (DoS)
🦉 Denial of Service (DoS)
🦉 More lessons are available in Snyk Learn

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants