Skip to content

[Snyk] Security upgrade ipython from 2.0.0 to 8.10.0#3

Open
snyk-bot wants to merge 1 commit intomasterfrom
snyk-fix-995cea5a18703ef053152e1ebf36551c
Open

[Snyk] Security upgrade ipython from 2.0.0 to 8.10.0#3
snyk-bot wants to merge 1 commit intomasterfrom
snyk-fix-995cea5a18703ef053152e1ebf36551c

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.development.txt

Vulnerabilities that will be fixed

By pinning:
Severity Priority Score (*) Issue Upgrade Breaking Change Exploit Maturity
high severity 624/1000
Why? Has a fix available, CVSS 8.2
Arbitrary Code Execution
SNYK-PYTHON-IPYTHON-2348630
ipython:
2.0.0 -> 8.10.0
No No Known Exploit
medium severity 603/1000
Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 4.2
Remote Code Execution (RCE)
SNYK-PYTHON-IPYTHON-3318382
ipython:
2.0.0 -> 8.10.0
No Proof of Concept
medium severity 519/1000
Why? Has a fix available, CVSS 6.1
Cross-site Scripting (XSS)
SNYK-PYTHON-IPYTHON-40329
ipython:
2.0.0 -> 8.10.0
No No Known Exploit
medium severity 519/1000
Why? Has a fix available, CVSS 6.1
Cross-site Scripting (XSS)
SNYK-PYTHON-IPYTHON-40330
ipython:
2.0.0 -> 8.10.0
No No Known Exploit
high severity 654/1000
Why? Has a fix available, CVSS 8.8
Cross-site Request Forgery (CSRF)
SNYK-PYTHON-IPYTHON-40338
ipython:
2.0.0 -> 8.10.0
No No Known Exploit
medium severity 509/1000
Why? Has a fix available, CVSS 5.9
Arbitrary Code Execution
SNYK-PYTHON-IPYTHON-40407
ipython:
2.0.0 -> 8.10.0
No No Known Exploit
medium severity 429/1000
Why? Has a fix available, CVSS 4.3
Cross-site Scripting (XSS)
SNYK-PYTHON-IPYTHON-40723
ipython:
2.0.0 -> 8.10.0
No No Known Exploit
medium severity 529/1000
Why? Has a fix available, CVSS 6.3
Arbitrary Code Execution
SNYK-PYTHON-IPYTHON-40724
ipython:
2.0.0 -> 8.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:

🦉 Cross-site Scripting (XSS)
🦉 Cross-site Scripting (XSS)
🦉 Cross-site Request Forgery (CSRF)
🦉 More lessons are available in Snyk Learn

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