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 16 vulnerabilities #42

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

Conversation

rmourey26
Copy link
Member

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-dev.txt
⚠️ Warning
web3 5.31.3 has requirement websockets<10,>=9.1, but you have websockets 11.0.3.
pythx 1.6.1 has requirement PyJWT<1.8.0,>=1.7.0, but you have PyJWT 2.8.0.
eth-keyfile 0.6.1 has requirement eth-keys<0.5.0,>=0.4.0, but you have eth-keys 0.3.4.
eth-keyfile 0.6.1 has requirement eth-utils<3,>=2, but you have eth-utils 1.10.0.
eth-brownie 1.19.3 requires vyper, which is not installed.
eth-brownie 1.19.3 has requirement attrs==22.1.0, but you have attrs 23.1.0.
eth-brownie 1.19.3 has requirement pathspec==0.10.1, but you have pathspec 0.11.2.
eth-brownie 1.19.3 has requirement eth-keyfile==0.5.1, but you have eth-keyfile 0.6.1.
eth-brownie 1.19.3 has requirement requests==2.28.1, but you have requests 2.31.0.
eth-brownie 1.19.3 has requirement websockets==9.1, but you have websockets 11.0.3.
eth-brownie 1.19.3 has requirement black==22.10.0, but you have black 19.10b0.
eth-brownie 1.19.3 has requirement aiohttp==3.8.3, but you have aiohttp 3.8.5.
eth-brownie 1.19.3 has requirement wheel==0.37.1, but you have wheel 0.41.2.
eth-brownie 1.19.3 has requirement certifi==2022.9.24, but you have certifi 2023.7.22.
eth-brownie 1.19.3 has requirement click==8.1.3, but you have click 8.1.7.
eth-account 0.5.9 has requirement eth-keyfile<0.6.0,>=0.5.0, but you have eth-keyfile 0.6.1.

Vulnerabilities that will be fixed

By pinning:
Severity Priority Score (*) Issue Upgrade Breaking Change Exploit Maturity
medium severity 586/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 5.3
HTTP Request Smuggling
SNYK-PYTHON-AIOHTTP-5798483
aiohttp:
3.8.3 -> 3.8.5
No Proof of Concept
medium severity 554/1000
Why? Has a fix available, CVSS 6.8
Insufficient Verification of Data Authenticity
SNYK-PYTHON-CERTIFI-3164749
certifi:
2022.9.24 -> 2023.7.22
No No Known Exploit
critical severity 704/1000
Why? Has a fix available, CVSS 9.8
Improper Following of a Certificate's Chain of Trust
SNYK-PYTHON-CERTIFI-5805047
certifi:
2022.9.24 -> 2023.7.22
No No Known Exploit
low severity 399/1000
Why? Has a fix available, CVSS 3.7
Timing Attack
SNYK-PYTHON-ETHKEYFILE-2391482
eth-keyfile:
0.5.1 -> 0.6.0
No No Known Exploit
medium severity 479/1000
Why? Has a fix available, CVSS 5.3
Regular Expression Denial of Service (ReDoS)
SNYK-PYTHON-PYGMENTS-5750273
pygments:
2.13.0 -> 2.15.0
No No Known Exploit
high severity 691/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 7.4
Use of a Broken or Risky Cryptographic Algorithm
SNYK-PYTHON-PYJWT-2840625
pyjwt:
1.7.1 -> 2.4.0
No Proof of Concept
medium severity 519/1000
Why? Has a fix available, CVSS 6.1
Information Exposure
SNYK-PYTHON-REQUESTS-5595532
requests:
2.28.1 -> 2.31.0
No No Known Exploit
medium severity 509/1000
Why? Has a fix available, CVSS 5.9
Regular Expression Denial of Service (ReDoS)
SNYK-PYTHON-SETUPTOOLS-3180412
setuptools:
39.0.1 -> 65.5.1
No No Known Exploit
high severity 686/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 7.3
Buffer Overflow
SNYK-PYTHON-VYPER-5498580
vyper:
0.3.7 -> 0.3.10rc4
No Proof of Concept
high severity 589/1000
Why? Has a fix available, CVSS 7.5
Function Call With Incorrect Order of Arguments
SNYK-PYTHON-VYPER-5529831
vyper:
0.3.7 -> 0.3.10rc4
No No Known Exploit
high severity 696/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 7.5
Out-of-bounds Write
SNYK-PYTHON-VYPER-5529832
vyper:
0.3.7 -> 0.3.10rc4
No Proof of Concept
high severity 589/1000
Why? Has a fix available, CVSS 7.5
Integer Overflow or Wraparound
SNYK-PYTHON-VYPER-5529833
vyper:
0.3.7 -> 0.3.10rc4
No No Known Exploit
low severity 399/1000
Why? Has a fix available, CVSS 3.7
Access Control Bypass
SNYK-PYTHON-VYPER-5591073
vyper:
0.3.7 -> 0.3.10rc4
No No Known Exploit
high severity 758/1000
Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 7.3
Improper Input Validation
SNYK-PYTHON-VYPER-5920076
vyper:
0.3.7 -> 0.3.10rc4
No Proof of Concept
medium severity 520/1000
Why? Has a fix available, CVSS 5.9
Denial of Service (DoS)
SNYK-PYTHON-WEBSOCKETS-1582792
websockets:
9.1 -> 10.0
No No Known Exploit
high severity 589/1000
Why? Has a fix available, CVSS 7.5
Regular Expression Denial of Service (ReDoS)
SNYK-PYTHON-WHEEL-3180413
wheel:
0.37.1 -> 0.38.0
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:

🦉 Regular Expression Denial of Service (ReDoS)
🦉 Use of a Broken or Risky Cryptographic Algorithm
🦉 Access Control Bypass
🦉 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