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

[Snyk] Security upgrade jwcrypto from 1.5.2 to 1.5.6 #12

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

Conversation

svc-ast-gh-snyk5
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:
    • dev/requirements_dev.txt
⚠️ Warning
github3.py 1.3.0 requires jwcrypto, which is not installed.
botocore 1.33.13 has requirement urllib3<1.27,>=1.25.4; python_version < "3.10", but you have urllib3 2.0.7.

Vulnerabilities that will be fixed

By pinning:
Severity Priority Score (*) Issue Upgrade Breaking Change Exploit Maturity
medium severity 733/1000
Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 6.8
Denial of Service (DoS)
SNYK-PYTHON-JWCRYPTO-6405821
jwcrypto:
1.5.2 -> 1.5.6
No Proof of Concept

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

The following vulnerabilities are fixed by pinning transitive dependencies:
- https://snyk.io/vuln/SNYK-PYTHON-JWCRYPTO-6405821
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants