Skip to content

[Snyk] Security upgrade scipy from 1.1.0 to 1.10.0rc1#119

Closed
terrorizer1980 wants to merge 1 commit intomasterfrom
snyk-fix-11f79588c23d1bccbda796297c151b06
Closed

[Snyk] Security upgrade scipy from 1.1.0 to 1.10.0rc1#119
terrorizer1980 wants to merge 1 commit intomasterfrom
snyk-fix-11f79588c23d1bccbda796297c151b06

Conversation

@terrorizer1980
Copy link
Copy Markdown
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:
    • sdks/python/apache_beam/testing/benchmarks/chicago_taxi/requirements.txt
⚠️ Warning
tensorflow-transform 0.13.0 has requirement protobuf<4,>=3.7, but you have protobuf 4.23.3.
tensorflow-model-analysis 0.13.2 requires scipy, which is not installed.
tensorflow-model-analysis 0.13.2 has requirement ipywidgets<8,>=7, but you have ipywidgets 8.0.7.
tensorflow-model-analysis 0.13.2 has requirement protobuf<4,>=3.7, but you have protobuf 4.23.3.
tensorflow-metadata 0.13.0 has requirement protobuf<4,>=3.7, but you have protobuf 4.23.3.
tensorflow-data-validation 0.13.1 has requirement absl-py<1,>=0.1.6, but you have absl-py 1.4.0.
tensorflow-data-validation 0.13.1 has requirement protobuf<4,>=3.7, but you have protobuf 4.23.3.
scikit-learn 0.24.2 requires scipy, which is not installed.
notebook 5.7.16 has requirement nbconvert<6.0, but you have nbconvert 7.6.0.
jupyter-console 6.6.3 has requirement jupyter-client>=7.0.0, but you have jupyter-client 6.2.0.
google-auth 2.21.0 has requirement urllib3<2.0, but you have urllib3 2.0.3.

Vulnerabilities that will be fixed

By pinning:
Severity Priority Score (*) Issue Upgrade Breaking Change Exploit Maturity
high severity 661/1000
Why? Recently disclosed, Has a fix available, CVSS 7.5
Denial of Service (DoS)
SNYK-PYTHON-SCIPY-5756497
scipy:
1.1.0 -> 1.10.0rc1
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)

…ents.txt to reduce vulnerabilities

The following vulnerabilities are fixed by pinning transitive dependencies:
- https://snyk.io/vuln/SNYK-PYTHON-SCIPY-5756497
@stale
Copy link
Copy Markdown

stale bot commented Sep 4, 2023

This pull request has been marked as stale due to 60 days of inactivity. It will be closed in 1 week if no further activity occurs. If you think that’s incorrect or this pull request requires a review, please simply write any comment. If closed, you can revive the PR at any time and @mention a reviewer or discuss it on the dev@beam.apache.org list. Thank you for your contributions.

@stale stale bot added the stale label Sep 4, 2023
@stale
Copy link
Copy Markdown

stale bot commented Sep 12, 2023

This pull request has been closed due to lack of activity. If you think that is incorrect, or the pull request requires review, you can revive the PR at any time.

@stale stale bot closed this Sep 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants