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] Security upgrade jupyter-server from 1.24.0 to 2.7.2 #679

Closed
wants to merge 1 commit into from

Conversation

bashtage
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:
    • requirements-dev.txt
⚠️ Warning
sphinx 5.3.0 has requirement docutils<0.20,>=0.14, but you have docutils 0.20.1.
seaborn 0.12.2 has requirement numpy!=1.24.0,>=1.17, but you have numpy 1.14.5.
pandas 1.3.5 has requirement numpy>=1.17.3; platform_machine != "aarch64" and platform_machine != "arm64" and python_version < "3.10", but you have numpy 1.14.5.
numba 0.56.4 has requirement numpy<1.24,>=1.18, but you have numpy 1.14.5.
matplotlib 3.5.3 has requirement numpy>=1.17, but you have numpy 1.14.5.
flake8 5.0.4 has requirement importlib-metadata<4.3,>=1.1.0; python_version < "3.8", but you have importlib-metadata 6.7.0.

Vulnerabilities that will be fixed

By pinning:
Severity Priority Score (*) Issue Upgrade Breaking Change Exploit Maturity
medium severity 516/1000
Why? Recently disclosed, Has a fix available, CVSS 4.6
Access Control Bypass
SNYK-PYTHON-JUPYTERSERVER-5862881
jupyter-server:
1.24.0 -> 2.7.2
No No Known Exploit
medium severity 501/1000
Why? Recently disclosed, Has a fix available, CVSS 4.3
Open Redirect
SNYK-PYTHON-JUPYTERSERVER-5862882
jupyter-server:
1.24.0 -> 2.7.2
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:

🦉 Access Control Bypass
🦉 Open Redirect

@codecov
Copy link

codecov bot commented Aug 29, 2023

Codecov Report

Patch coverage has no change and project coverage change: -0.11% ⚠️

Comparison is base (98a2bfa) 99.43% compared to head (b544c56) 99.33%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #679      +/-   ##
==========================================
- Coverage   99.43%   99.33%   -0.11%     
==========================================
  Files          74       74              
  Lines       15509    15495      -14     
  Branches     2086     1350     -736     
==========================================
- Hits        15422    15392      -30     
- Misses         63       71       +8     
- Partials       24       32       +8     

see 6 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@bashtage bashtage closed this Sep 27, 2023
@bashtage bashtage deleted the snyk-fix-689ca182bf1a2d9ca923aeb0724c7443 branch January 2, 2024 14:24
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