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 11 vulnerabilities #2

Merged
merged 1 commit into from
Dec 8, 2023

Conversation

philipphomberger
Copy link
Owner

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:
    • st2common/requirements.txt
⚠️ Warning
requests 2.25.1 has requirement chardet<5,>=3.0.2, but you have chardet 5.2.0.
pyOpenSSL 23.1.0 has requirement cryptography<41,>=38.0.0, but you have cryptography 41.0.6.
orquesta 1.2.0 has requirement networkx<2.0,>=1.10, but you have networkx 2.6.3.

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-5663682
cryptography:
39.0.1 -> 41.0.6
No No Known Exploit
high severity 691/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 7.4
Improper Certificate Validation
SNYK-PYTHON-CRYPTOGRAPHY-5777683
cryptography:
39.0.1 -> 41.0.6
No Proof of Concept
low severity 399/1000
Why? Has a fix available, CVSS 3.7
Insufficient Verification of Data Authenticity
SNYK-PYTHON-CRYPTOGRAPHY-5813745
cryptography:
39.0.1 -> 41.0.6
No No Known Exploit
medium severity 479/1000
Why? Has a fix available, CVSS 5.3
Denial of Service (DoS)
SNYK-PYTHON-CRYPTOGRAPHY-5813746
cryptography:
39.0.1 -> 41.0.6
No No Known Exploit
low severity 399/1000
Why? Has a fix available, CVSS 3.7
Denial of Service (DoS)
SNYK-PYTHON-CRYPTOGRAPHY-5813750
cryptography:
39.0.1 -> 41.0.6
No No Known Exploit
medium severity 539/1000
Why? Has a fix available, CVSS 6.5
Denial of Service (DoS)
SNYK-PYTHON-CRYPTOGRAPHY-5914629
cryptography:
39.0.1 -> 41.0.6
No No Known Exploit
medium severity 479/1000
Why? Has a fix available, CVSS 5.3
Missing Cryptographic Step
SNYK-PYTHON-CRYPTOGRAPHY-6036192
cryptography:
39.0.1 -> 41.0.6
No No Known Exploit
medium severity 688/1000
Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 5.9
NULL Pointer Dereference
SNYK-PYTHON-CRYPTOGRAPHY-6092044
cryptography:
39.0.1 -> 41.0.6
No Proof of Concept
low severity 506/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 3.7
Exposure of Data Element to Wrong Session
SNYK-PYTHON-REDIS-5291195
redis:
4.1.4 -> 4.3.6
No Proof of Concept
medium severity 519/1000
Why? Has a fix available, CVSS 6.1
Information Exposure
SNYK-PYTHON-REQUESTS-5595532
requests:
2.25.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

(*) 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)
🦉 NULL Pointer Dereference

@philipphomberger philipphomberger merged commit 88394ac into master Dec 8, 2023
1 check was pending
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants