patil215
[Snyk] Fix for 12 vulnerabilities
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:
- webapp/requirements.txt
⚠️ Warning
Pyrebase 3.0.27 has requirement python-jwt==2.0.1, but you have python-jwt 3.3.5.
Pyrebase 3.0.27 has requirement oauth2client==3.0.0, but you have oauth2client 4.0.0.
Pyrebase 3.0.27 has requirement requests==2.11.1, but you have requests 2.20.0.
Pyrebase 3.0.27 has requirement pycryptodome==3.4.3, but you have pycryptodome 3.15.0.
pycaption 1.0.0 requires lxml, which is not installed.
oauth2client 4.0.0 requires rsa, which is not installed.
httplib2 0.19.0 has requirement pyparsing<3,>=2.4.2, but you have pyparsing 2.1.10.
googleapis-common-protos 1.5.2 requires protobuf, which is not installed.
google-gax 0.16.0 requires protobuf, which is not installed.
google-gax 0.16.0 requires grpcio, which is not installed.
google-gax 0.16.0 has requirement google-auth<2.0dev,>=1.0.0, but you have google-auth 0.7.0.
google-gax 0.16.0 has requirement future<0.17dev,>=0.16.0, but you have future 0.18.2.
google-cloud-core 0.22.1 requires protobuf, which is not installed.
google-auth 0.7.0 requires rsa, which is not installed.
google-auth-httplib2 0.0.2 requires rsa, which is not installed.
gcloud 0.17.0 requires gax-google-logging-v2, which is not installed.
gcloud 0.17.0 requires grpcio, which is not installed.
gcloud 0.17.0 requires protobuf, which is not installed.
gax-google-pubsub-v1 0.8.3 requires grpc-google-pubsub-v1, which is not installed.
gax-google-pubsub-v1 0.8.3 has requirement google-gax<0.13.0,>=0.12.5, but you have google-gax 0.16.0.
Flask-SQLAlchemy 2.5.1 requires SQLAlchemy, which is not installed.
alembic 1.6.5 requires SQLAlchemy, which is not installed.
Vulnerabilities that will be fixed
By pinning:
| Severity | Priority Score (*) | Issue | Upgrade | Breaking Change | Exploit Maturity |
|---|---|---|---|---|---|
 |
589/1000 Why? Has a fix available, CVSS 7.5 |
Regular Expression Denial of Service (ReDoS) SNYK-PYTHON-HTTPLIB2-1065795 |
httplib2: 0.10.3 -> 0.19.0 |
No | No Known Exploit |
 |
554/1000 Why? Has a fix available, CVSS 6.8 |
CRLF Injection SNYK-PYTHON-HTTPLIB2-569758 |
httplib2: 0.10.3 -> 0.19.0 |
No | No Known Exploit |
|
624/1000 Why? Has a fix available, CVSS 8.2 |
CRLF Injection SNYK-PYTHON-HTTPLIB2-570767 |
httplib2: 0.10.3 -> 0.19.0 |
No | No Known Exploit |
|
499/1000 Why? Has a fix available, CVSS 5.7 |
Denial of Service (DoS) SNYK-PYTHON-PROTOBUF-3031740 |
protobuf: 3.2.0 -> 3.18.3 |
No | No Known Exploit |
|
654/1000 Why? Has a fix available, CVSS 8.8 |
Integer Overflow SNYK-PYTHON-PROTOBUF-472377 |
protobuf: 3.2.0 -> 3.18.3 |
No | No Known Exploit |
|
509/1000 Why? Has a fix available, CVSS 5.9 |
Insecure Encryption SNYK-PYTHON-PYCRYPTODOME-3012886 |
pycryptodome: 3.4.3 -> 3.6.6 |
No | No Known Exploit |
|
509/1000 Why? Has a fix available, CVSS 5.9 |
Deprecated Cypher SNYK-PYTHON-PYCRYPTODOME-40784 |
pycryptodome: 3.4.3 -> 3.6.6 |
No | No Known Exploit |
|
589/1000 Why? Has a fix available, CVSS 7.5 |
Denial of Service (DoS) SNYK-PYTHON-PYCRYPTODOME-42184 |
pycryptodome: 3.4.3 -> 3.6.6 |
No | No Known Exploit |
|
509/1000 Why? Has a fix available, CVSS 5.9 |
Authentication Bypass SNYK-PYTHON-PYTHONJWT-3017172 |
python-jwt: 2.0.1 -> 3.3.4 |
No | No Known Exploit |
 |
811/1000 Why? Proof of Concept exploit, Has a fix available, CVSS 9.8 |
Information Exposure SNYK-PYTHON-REQUESTS-72435 |
requests: 2.13.0 -> 2.20 |
No | Proof of Concept |
|
589/1000 Why? Has a fix available, CVSS 7.5 |
Timing Attack SNYK-PYTHON-RSA-1038401 |
rsa: 3.4.2 -> 4.7 |
No | No Known Exploit |
|
494/1000 Why? Has a fix available, CVSS 5.6 |
Access Restriction Bypass SNYK-PYTHON-RSA-570831 |
rsa: 3.4.2 -> 4.7 |
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
📚 Read more about Snyk's upgrade and patch logic
Learn how to fix vulnerabilities with free interactive lessons:
🦉 Regular Expression Denial of Service (ReDoS) 🦉 CRLF Injection 🦉 CRLF Injection 🦉 More lessons are available in Snyk Learn
