[Snyk] Fix for 2 vulnerabilities

[Bsingstad]

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.

✨ Snyk has automatically assigned this pull request, set who gets assigned.

As this is a private repository, Snyk-bot does not have access. Therefore, this PR has been created automatically, but appears to have been created by a real user.

Changes included in this PR

• Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
  • requirements.txt

⚠️ Warning

ipykernel 6.14.0 requires ipython, which is not installed.
flake8 4.0.1 has requirement importlib-metadata<4.3; python_version < "3.8", but you have importlib-metadata 4.11.4.
tensorboard 2.9.1 has requirement setuptools>=41.0.0, but you have setuptools 40.5.0.
virtualenv 20.25.1 has requirement distlib<1,>=0.3.7, but you have distlib 0.3.4.
virtualenv 20.25.1 has requirement filelock<4,>=3.12.2, but you have filelock 3.7.1.
virtualenv 20.25.1 has requirement importlib-metadata>=6.6; python_version < "3.8", but you have importlib-metadata 4.11.4.
virtualenv 20.25.1 has requirement platformdirs<5,>=3.9.1, but you have platformdirs 2.5.2.

Vulnerabilities that will be fixed

By pinning:

Severity	Priority Score (*)	Issue	Upgrade	Breaking Change	Exploit Maturity
	658/1000 Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 5.3	Regular Expression Denial of Service (ReDoS) SNYK-PYTHON-BLACK-6256273	black: 22.3.0 -> 24.3.0	No	Proof of Concept
	776/1000 Why? Proof of Concept exploit, Has a fix available, CVSS 9.1	Arbitrary File Write via Archive Extraction (Zip Slip) SNYK-PYTHON-TENSORFLOW-1315149	tensorflow: 2.9.1 -> 2.12.0rc1	No	Proof of Concept

(*) 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

👩‍💻 Set who automatically gets assigned

🛠 Adjust project settings

📚 Read more about Snyk's upgrade and patch logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Regular Expression Denial of Service (ReDoS)