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 3 vulnerabilities #24

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

Conversation

snyk-bot
Copy link

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
web3 5.31.1 requires aiohttp, which is not installed.
web3 5.31.1 has requirement eth-utils<2.0.0,>=1.9.5, but you have eth-utils 2.0.0.
web3 5.31.1 has requirement websockets<10,>=9.1, but you have websockets 10.4.
web3 5.31.1 has requirement ipfshttpclient==0.8.0a2, but you have ipfshttpclient 0.7.0.
s3transfer 0.6.0 requires botocore, which is not installed.
pythx 1.6.1 has requirement PyJWT<1.8.0,>=1.7.0, but you have PyJWT 2.6.0.
nltk 3.7 requires regex, which is not installed.
matplotlib 3.5.3 requires numpy, which is not installed.
matplotlib 3.5.3 requires pillow, which is not installed.
eth-utils 2.0.0 requires cytoolz, which is not installed.
eth-utils 2.0.0 has requirement eth-typing<4.0.0,>=3.0.0, but you have eth-typing 2.3.0.
eth-rlp 0.2.1 requires rlp, which is not installed.
eth-rlp 0.2.1 has requirement eth-utils<2,>=1.0.1, but you have eth-utils 2.0.0.
eth-keys 0.3.4 has requirement eth-utils<2.0.0,>=1.8.2, but you have eth-utils 2.0.0.
eth-keyfile 0.6.0 has requirement eth-keys<0.5.0,>=0.4.0, but you have eth-keys 0.3.4.
eth-event 1.2.3 has requirement eth-utils<2.0.0,>=1.2.0, but you have eth-utils 2.0.0.
eth-brownie 1.19.2 requires py-solc-ast, which is not installed.
eth-brownie 1.19.2 requires rlp, which is not installed.
eth-brownie 1.19.2 requires aiohttp, which is not installed.
eth-brownie 1.19.2 requires cytoolz, which is not installed.
eth-brownie 1.19.2 requires hypothesis, which is not installed.
eth-brownie 1.19.2 has requirement websockets==9.1, but you have websockets 10.4.
eth-brownie 1.19.2 has requirement python-dotenv==0.16.0, but you have python-dotenv 0.21.0.
eth-brownie 1.19.2 has requirement eth-keyfile==0.5.1, but you have eth-keyfile 0.6.0.
eth-brownie 1.19.2 has requirement pytest==6.2.5, but you have pytest 7.2.0.
eth-brownie 1.19.2 has requirement eth-utils==1.10.0, but you have eth-utils 2.0.0.
eth-brownie 1.19.2 has requirement ipfshttpclient==0.8.0a2, but you have ipfshttpclient 0.7.0.
eth-account 0.5.9 requires rlp, which is not installed.
eth-account 0.5.9 has requirement eth-utils<2,>=1.3.0, but you have eth-utils 2.0.0.
eth-account 0.5.9 has requirement eth-keyfile<0.6.0,>=0.5.0, but you have eth-keyfile 0.6.0.
eth-abi 2.2.0 has requirement eth-utils<2.0.0,>=1.2.0, but you have eth-utils 2.0.0.
envelope 2.0.0 requires py3-validate-email, which is not installed.
eip712 0.1.0 has requirement eth-utils<2,>=1.3.0, but you have eth-utils 2.0.0.
boto3 1.25.5 requires botocore, which is not installed.
ascii-magic 1.6 requires Pillow, which is not installed.

Vulnerabilities that will be fixed

By pinning:
Severity Priority Score (*) Issue Upgrade Breaking Change Exploit Maturity
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
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 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

(*) 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:

🦉 Use of a Broken or Risky Cryptographic Algorithm
🦉 Denial of Service (DoS)

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.

1 participant