Skip to content
This repository has been archived by the owner on Oct 30, 2023. It is now read-only.

[Snyk] Fix for 3 vulnerabilities #71

Closed
wants to merge 1 commit into from

Conversation

yu-iskw
Copy link
Owner

@yu-iskw yu-iskw commented Oct 16, 2023

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:
    • requirements/requirements.txt
⚠️ Warning
openapi-spec-validator 0.3.3 has requirement jsonschema<4.0.0,>=3.2.0, but you have jsonschema 4.17.3.
hologram 0.0.15 has requirement jsonschema<4.0,>=3.0, but you have jsonschema 4.17.3.
grpcio-status 1.59.0 has requirement protobuf>=4.21.6, but you have protobuf 3.20.3.
fastapi 0.70.1 has requirement starlette==0.16.0, but you have starlette 0.29.0.
dbt-bigquery 1.4.3 has requirement google-cloud-bigquery~=3.0, but you have google-cloud-bigquery 2.34.4.
black 23.3.0 has requirement packaging>=22.0, but you have packaging 21.3.
argcomplete 2.1.2 has requirement importlib-metadata<6,>=0.23; python_version == "3.7", but you have importlib-metadata 6.7.0.

Vulnerabilities that will be fixed

By pinning:
Severity Priority Score (*) Issue Upgrade Breaking Change Exploit Maturity
medium severity 509/1000
Why? Has a fix available, CVSS 5.9
Regular Expression Denial of Service (ReDoS)
SNYK-PYTHON-SETUPTOOLS-3180412
setuptools:
39.0.1 -> 65.5.1
No No Known Exploit
medium severity 509/1000
Why? Has a fix available, CVSS 5.9
Denial of Service (DoS)
SNYK-PYTHON-STARLETTE-3319937
starlette:
0.16.0 -> 0.27.0
No No Known Exploit
high severity 696/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 7.5
Directory Traversal
SNYK-PYTHON-STARLETTE-5538332
starlette:
0.16.0 -> 0.27.0
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

🛠 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)
🦉 Directory Traversal

@yu-iskw yu-iskw closed this Oct 17, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants