zehengl / ezapi-tmdb

A Python wrapper for TMDb API
https://pypi.python.org/pypi/ezapi-tmdb
MIT License
10 stars 1 forks source link

[Snyk] Security upgrade pillow from 6.2.2 to 8.1.0 #13

Closed snyk-bot closed 3 years ago

snyk-bot commented 3 years ago

Snyk has created this PR to fix one or more vulnerable packages in the `pip` dependencies of this project.

Changes included in this PR

⚠️ Warning ``` seleniumbase 1.64.1 requires pillow, which is not installed. ```

Vulnerabilities that will be fixed

By pinning:
Severity Priority Score (*) Issue Upgrade Breaking Change Exploit Maturity
high severity 589/1000
Why? Has a fix available, CVSS 7.5
Out-of-bounds Read
SNYK-PYTHON-PILLOW-1055461
pillow:
6.2.2 -> 8.1.0
No No Known Exploit
high severity 589/1000
Why? Has a fix available, CVSS 7.5
Out-of-bounds Read
SNYK-PYTHON-PILLOW-1055462
pillow:
6.2.2 -> 8.1.0
No No Known Exploit
medium severity 509/1000
Why? Has a fix available, CVSS 5.9
Out-of-bounds Write
SNYK-PYTHON-PILLOW-1059090
pillow:
6.2.2 -> 8.1.0
No No Known Exploit
high severity 589/1000
Why? Has a fix available, CVSS 7.5
Out-of-bounds Read
SNYK-PYTHON-PILLOW-1080635
pillow:
6.2.2 -> 8.1.0
No No Known Exploit
high severity 589/1000
Why? Has a fix available, CVSS 7.5
Regular Expression Denial of Service (ReDoS)
SNYK-PYTHON-PILLOW-1080654
pillow:
6.2.2 -> 8.1.0
No No Known Exploit
high severity 589/1000
Why? Has a fix available, CVSS 7.5
Denial of Service (DoS)
SNYK-PYTHON-PILLOW-1081494
pillow:
6.2.2 -> 8.1.0
No No Known Exploit
high severity 589/1000
Why? Has a fix available, CVSS 7.5
Denial of Service (DoS)
SNYK-PYTHON-PILLOW-1081501
pillow:
6.2.2 -> 8.1.0
No No Known Exploit
high severity 589/1000
Why? Has a fix available, CVSS 7.5
Denial of Service (DoS)
SNYK-PYTHON-PILLOW-1081502
pillow:
6.2.2 -> 8.1.0
No No Known Exploit
high severity 654/1000
Why? Has a fix available, CVSS 8.8
Heap-based Buffer Overflow
SNYK-PYTHON-PILLOW-1082329
pillow:
6.2.2 -> 8.1.0
No No Known Exploit
high severity 589/1000
Why? Has a fix available, CVSS 7.5
Insufficient Validation
SNYK-PYTHON-PILLOW-1082750
pillow:
6.2.2 -> 8.1.0
No No Known Exploit
high severity 589/1000
Why? Has a fix available, CVSS 7.5
Denial of Service (DoS)
SNYK-PYTHON-PILLOW-1090584
pillow:
6.2.2 -> 8.1.0
No No Known Exploit
high severity 589/1000
Why? Has a fix available, CVSS 7.5
Denial of Service (DoS)
SNYK-PYTHON-PILLOW-1090586
pillow:
6.2.2 -> 8.1.0
No No Known Exploit
high severity 589/1000
Why? Has a fix available, CVSS 7.5
Denial of Service (DoS)
SNYK-PYTHON-PILLOW-1090587
pillow:
6.2.2 -> 8.1.0
No No Known Exploit
high severity 589/1000
Why? Has a fix available, CVSS 7.5
Denial of Service (DoS)
SNYK-PYTHON-PILLOW-1090588
pillow:
6.2.2 -> 8.1.0
No No Known Exploit
high severity 589/1000
Why? Has a fix available, CVSS 7.5
Out-of-bounds Read
SNYK-PYTHON-PILLOW-1292150
pillow:
6.2.2 -> 8.1.0
No No Known Exploit
high severity 589/1000
Why? Has a fix available, CVSS 7.5
Out-of-bounds Read
SNYK-PYTHON-PILLOW-1292151
pillow:
6.2.2 -> 8.1.0
No No Known Exploit
medium severity 494/1000
Why? Has a fix available, CVSS 5.6
Buffer Overflow
SNYK-PYTHON-PILLOW-1316216
pillow:
6.2.2 -> 8.1.0
No No Known Exploit
high severity 661/1000
Why? Recently disclosed, Has a fix available, CVSS 7.5
Regular Expression Denial of Service (ReDoS)
SNYK-PYTHON-PILLOW-1319443
pillow:
6.2.2 -> 8.1.0
No No Known Exploit
medium severity 414/1000
Why? Has a fix available, CVSS 4
Out-of-Bounds
SNYK-PYTHON-PILLOW-574573
pillow:
6.2.2 -> 8.1.0
No No Known Exploit
medium severity 414/1000
Why? Has a fix available, CVSS 4
Out-of-bounds Read
SNYK-PYTHON-PILLOW-574574
pillow:
6.2.2 -> 8.1.0
No No Known Exploit
medium severity 414/1000
Why? Has a fix available, CVSS 4
Out-of-bounds Read
SNYK-PYTHON-PILLOW-574575
pillow:
6.2.2 -> 8.1.0
No No Known Exploit
medium severity 414/1000
Why? Has a fix available, CVSS 4
Out-of-bounds Read
SNYK-PYTHON-PILLOW-574576
pillow:
6.2.2 -> 8.1.0
No No Known Exploit
medium severity 469/1000
Why? Has a fix available, CVSS 5.1
Buffer Overflow
SNYK-PYTHON-PILLOW-574577
pillow:
6.2.2 -> 8.1.0
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 effected 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