Skip to content

[Snyk] Security upgrade tensorflow from 2.10.0 to 2.11.1#33

Open
Centaurioun wants to merge 2 commits into
masterfrom
snyk-fix-cc68ebd7ab745cbafac3a280579e3efa
Open

[Snyk] Security upgrade tensorflow from 2.10.0 to 2.11.1#33
Centaurioun wants to merge 2 commits into
masterfrom
snyk-fix-cc68ebd7ab745cbafac3a280579e3efa

Conversation

@Centaurioun

@Centaurioun Centaurioun commented Mar 29, 2023

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:
    • backends/stable_diffusion_tf/requirements.txt

Vulnerabilities that will be fixed

By pinning:
Severity Priority Score (*) Issue Upgrade Breaking Change Exploit Maturity
high severity 768/1000
Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 7.5		 NULL Pointer Dereference
SNYK-PYTHON-TENSORFLOW-3372984		 tensorflow:
2.10.0 -> 2.11.1
No Proof of Concept
high severity 768/1000
Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 7.5		 Out-of-bounds Read
SNYK-PYTHON-TENSORFLOW-3372987		 tensorflow:
2.10.0 -> 2.11.1
No Proof of Concept
high severity 768/1000
Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 7.5		 Out-of-bounds Read
SNYK-PYTHON-TENSORFLOW-3372990		 tensorflow:
2.10.0 -> 2.11.1
No Proof of Concept
high severity 768/1000
Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 7.5		 Denial of Service (DoS)
SNYK-PYTHON-TENSORFLOW-3372993		 tensorflow:
2.10.0 -> 2.11.1
No Proof of Concept
medium severity 688/1000
Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 5.9		 NULL Pointer Dereference
SNYK-PYTHON-TENSORFLOW-3372996		 tensorflow:
2.10.0 -> 2.11.1
No Proof of Concept
high severity 793/1000
Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 8		 Double Free
SNYK-PYTHON-TENSORFLOW-3372999		 tensorflow:
2.10.0 -> 2.11.1
No Proof of Concept
high severity 768/1000
Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 7.5		 Denial of Service (DoS)
SNYK-PYTHON-TENSORFLOW-3373002		 tensorflow:
2.10.0 -> 2.11.1
No Proof of Concept
high severity 768/1000
Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 7.5		 NULL Pointer Dereference
SNYK-PYTHON-TENSORFLOW-3373005		 tensorflow:
2.10.0 -> 2.11.1
No Proof of Concept
high severity 768/1000
Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 7.5		 Denial of Service (DoS)
SNYK-PYTHON-TENSORFLOW-3373008		 tensorflow:
2.10.0 -> 2.11.1
No Proof of Concept
high severity 661/1000
Why? Recently disclosed, Has a fix available, CVSS 7.5		 Out-of-Bounds
SNYK-PYTHON-TENSORFLOW-3373011		 tensorflow:
2.10.0 -> 2.11.1
No No Known Exploit
high severity 758/1000
Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 7.3		 Integer Overflow or Wraparound
SNYK-PYTHON-TENSORFLOW-3373014		 tensorflow:
2.10.0 -> 2.11.1
No Proof of Concept
medium severity 718/1000
Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 6.5		 Integer Overflow to Buffer Overflow
SNYK-PYTHON-TENSORFLOW-3373017		 tensorflow:
2.10.0 -> 2.11.1
No Proof of Concept
high severity 768/1000
Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 7.5		 Heap-based Buffer Overflow
SNYK-PYTHON-TENSORFLOW-3373020		 tensorflow:
2.10.0 -> 2.11.1
No Proof of Concept
high severity 768/1000
Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 7.5		 Buffer Overflow
SNYK-PYTHON-TENSORFLOW-3373023		 tensorflow:
2.10.0 -> 2.11.1
No Proof of Concept
high severity 768/1000
Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 7.5		 Denial of Service (DoS)
SNYK-PYTHON-TENSORFLOW-3373026		 tensorflow:
2.10.0 -> 2.11.1
No Proof of Concept
high severity 661/1000
Why? Recently disclosed, Has a fix available, CVSS 7.5		 Incorrect Comparison
SNYK-PYTHON-TENSORFLOW-3373029		 tensorflow:
2.10.0 -> 2.11.1
No No Known Exploit
high severity 661/1000
Why? Recently disclosed, Has a fix available, CVSS 7.5		 NULL Pointer Dereference
SNYK-PYTHON-TENSORFLOW-3373032		 tensorflow:
2.10.0 -> 2.11.1
No No Known Exploit
high severity 768/1000
Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 7.5		 Denial of Service (DoS)
SNYK-PYTHON-TENSORFLOW-3373035		 tensorflow:
2.10.0 -> 2.11.1
No Proof of Concept
high severity 768/1000
Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 7.5		 NULL Pointer Dereference
SNYK-PYTHON-TENSORFLOW-3373038		 tensorflow:
2.10.0 -> 2.11.1
No Proof of Concept
high severity 768/1000
Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 7.5		 Denial of Service (DoS)
SNYK-PYTHON-TENSORFLOW-3373041		 tensorflow:
2.10.0 -> 2.11.1
No Proof of Concept
medium severity 611/1000
Why? Recently disclosed, Has a fix available, CVSS 6.5		 Denial of Service (DoS)
SNYK-PYTHON-TENSORFLOW-5291376		 tensorflow:
2.10.0 -> 2.11.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:

🦉 NULL Pointer Dereference
🦉 Denial of Service (DoS)

@snyk-bot
fix: backends/stable_diffusion_tf/requirements.txt to reduce vulnerab…
803e43b 
…ilities

The following vulnerabilities are fixed by pinning transitive dependencies:
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-3372984
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-3372987
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-3372990
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-3372993
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-3372996
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-3372999
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-3373002
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-3373005
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-3373008
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-3373011
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-3373014
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-3373017
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-3373020
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-3373023
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-3373026
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-3373029
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-3373032
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-3373035
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-3373038
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-3373041
- https://snyk.io/vuln/SNYK-PYTHON-TENSORFLOW-5291376
@restyled-io restyled-io Bot mentioned this pull request Mar 29, 2023
Merged
@sonarqubecloud

sonarqubecloud Bot commented Mar 29, 2023

Copy link
Copy Markdown

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

@restyled-io @restyled-commits
Restyled by whitespace (#34)
c250a5c 
Co-authored-by: Restyled.io <commits@restyled.io>
@sonarqubecloud

sonarqubecloud Bot commented Aug 30, 2023

Copy link
Copy Markdown

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

@mergify

mergify Bot commented Aug 17, 2025

Copy link
Copy Markdown

This pull request has been removed from the queue for the following reason: pull request branch update failed.

The pull request can't be updated.

You should update or rebase your pull request manually. If you do, this pull request will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@Centaurioun @snyk-bot