[Snyk] Security upgrade tensorflow/tensorflow from latest to 2.15.0rc0

[AdamOswald]

This PR was automatically created by Snyk using the credentials of a real user.

Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of your chosen image. #### Changes included in this PR - Dockerfile.cpu We recommend upgrading to `tensorflow/tensorflow:2.15.0rc0`, as this image has only 56 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected. Some of the most important vulnerabilities in your base image include: | Severity | Priority Score / 1000 | Issue | Exploit Maturity | | :------: | :-------------------- | :---- | :--------------- | |  | **733** | Heap-based Buffer Overflow
[SNYK-UBUNTU2204-CURL-5960738](https://snyk.io/vuln/SNYK-UBUNTU2204-CURL-5960738) | No Known Exploit | |  | **733** | Heap-based Buffer Overflow
[SNYK-UBUNTU2204-CURL-5960738](https://snyk.io/vuln/SNYK-UBUNTU2204-CURL-5960738) | No Known Exploit | |  | **733** | Heap-based Buffer Overflow
[SNYK-UBUNTU2204-CURL-5960738](https://snyk.io/vuln/SNYK-UBUNTU2204-CURL-5960738) | No Known Exploit | |  | **721** | Out-of-bounds Write
[SNYK-UBUNTU2204-GLIBC-5927362](https://snyk.io/vuln/SNYK-UBUNTU2204-GLIBC-5927362) | Proof of Concept | |  | **721** | Out-of-bounds Write
[SNYK-UBUNTU2204-GLIBC-5927362](https://snyk.io/vuln/SNYK-UBUNTU2204-GLIBC-5927362) | Proof of Concept | --- **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](https://app.snyk.io/org/adamoswald/project/411005f7-01d3-41e3-befb-a858a18f9ed2?utm_source=github&utm_medium=referral&page=fix-pr) 🛠 [Adjust project settings](https://app.snyk.io/org/adamoswald/project/411005f7-01d3-41e3-befb-a858a18f9ed2?utm_source=github&utm_medium=referral&page=fix-pr/settings) [//]: # 'snyk:metadata:{"prId":"d9db9de2-a6fe-4e29-a8cf-d3d20ddc2361","prPublicId":"d9db9de2-a6fe-4e29-a8cf-d3d20ddc2361","dependencies":[{"name":"tensorflow/tensorflow","from":"latest","to":"2.15.0rc0"}],"packageManager":"dockerfile","projectPublicId":"411005f7-01d3-41e3-befb-a858a18f9ed2","projectUrl":"https://app.snyk.io/org/adamoswald/project/411005f7-01d3-41e3-befb-a858a18f9ed2?utm_source=github&utm_medium=referral&page=fix-pr","type":"auto","patch":[],"vulns":["SNYK-UBUNTU2204-CURL-5960738","SNYK-UBUNTU2204-GLIBC-5927362"],"upgrade":["SNYK-UBUNTU2204-CURL-5960738","SNYK-UBUNTU2204-CURL-5960738","SNYK-UBUNTU2204-CURL-5960738","SNYK-UBUNTU2204-GLIBC-5927362","SNYK-UBUNTU2204-GLIBC-5927362"],"isBreakingChange":false,"env":"prod","prType":"fix","templateVariants":["updated-fix-title","priorityScore"],"priorityScoreList":[733,721],"remediationStrategy":"vuln"}' --- **Learn how to fix vulnerabilities with free interactive lessons:** 🦉 [Learn about vulnerability in an interactive lesson of Snyk Learn.](https://learn.snyk.io/?loc=fix-pr)

[pull-request-quantifier-deprecated[bot]]

This PR has 2 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

``` Label : Extra Small Size : +1 -1 Percentile : 0.8% Total files changed: 1 Change summary by file extension: .cpu : +1 -1 ``` > Change counts above are quantified counts, based on the [PullRequestQuantifier customizations](https://github.com/microsoft/PullRequestQuantifier/blob/main/docs/prquantifier-yaml.md).

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a balance between between PR complexity and PR review overhead. PRs within the optimal size (typical small, or medium sized PRs) mean: - Fast and predictable releases to production: - Optimal size changes are more likely to be reviewed faster with fewer iterations. - Similarity in low PR complexity drives similar review times. - Review quality is likely higher as complexity is lower: - Bugs are more likely to be detected. - Code inconsistencies are more likely to be detected. - Knowledge sharing is improved within the participants: - Small portions can be assimilated better. - Better engineering practices are exercised: - Solving big problems by dividing them in well contained, smaller problems. - Exercising separation of concerns within the code changes. #### What can I do to optimize my changes - Use the PullRequestQuantifier to quantify your PR accurately - Create a context profile for your repo using the [context generator](https://github.com/microsoft/PullRequestQuantifier/releases) - Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the `Excluded` section from your `prquantifier.yaml` context profile. - Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your `prquantifier.yaml` context profile. - Only use the labels that matter to you, [see context specification](./docs/prquantifier-yaml.md) to customize your `prquantifier.yaml` context profile. - Change your engineering behaviors - For PRs that fall outside of the desired spectrum, review the details and check if: - Your PR could be split in smaller, self-contained PRs instead - Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR). #### How to interpret the change counts in git diff output - One line was added: `+1 -0` - One line was deleted: `+0 -1` - One line was modified: `+1 -1` (git diff doesn't know about modified, it will interpret that line like one addition plus one deletion) - Change percentiles: Change characteristics (addition, deletion, modification) of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? :thumbsup:  :ok_hand:  :thumbsdown: (Email) Customize PullRequestQuantifier for this repository.

[secure-code-warrior-for-github[bot]]

Micro-Learning Topic: Buffer overflow (Detected by phrase)

Matched on "Buffer Overflow"

What is this? (2min video)

A buffer overflow condition exists when a program attempts to put more data in a buffer than it can hold or when a program attempts to put data in a memory area past a buffer.

Try a challenge in Secure Code Warrior

Micro-Learning Topic: Heap-based buffer overflow (Detected by phrase)

Matched on "Heap-based Buffer Overflow"

What is this? (2min video)

Also referred to as Heap buffer overflows. Memory buffers, arrays and strings allocated from the heap are prime candidates for this type of overflow vulnerability.

Try a challenge in Secure Code Warrior

[performance-testing-bot[bot]]

Unable to verify url with installation ID

[senior-dev-bot[bot]]

Hi there! :wave: Thanks for opening a PR. :tada: To get the most out of Senior Dev, please uninstall the app from your organization, then re-install it into your organization. You can uninstall the app here :rocket:

[difflens[bot]]

View changes in DiffLens

[viezly[bot]]

Changes preview:

Legend:

👀 Review pull request on Viezly

[sonarcloud[bot]]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication