Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Snyk] Security upgrade lxml from 3.4.0 to 4.9.1 #198

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

twilio-product-security

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.txt
⚠️ Warning
xmlunittest 0.3.2 has requirement lxml<4.0.0,>=2.3, but you have lxml 4.9.1.
Flask-SQLAlchemy 2.1 requires SQLAlchemy, which is not installed.
alembic 1.6.5 requires SQLAlchemy, which is not installed.

Vulnerabilities that will be fixed

By pinning:
Severity Priority Score (*) Issue Upgrade Breaking Change Exploit Maturity
high severity 579/1000
Why? Has a fix available, CVSS 7.3
Cross-site Scripting (XSS)
SNYK-PYTHON-LXML-1047473
lxml:
3.4.0 -> 4.9.1
No No Known Exploit
medium severity 479/1000
Why? Has a fix available, CVSS 5.3
Arbitrary File Write
SNYK-PYTHON-LXML-1047474
lxml:
3.4.0 -> 4.9.1
No No Known Exploit
medium severity 529/1000
Why? Has a fix available, CVSS 6.3
Cross-site Scripting (XSS)
SNYK-PYTHON-LXML-1088006
lxml:
3.4.0 -> 4.9.1
No No Known Exploit
high severity 624/1000
Why? Has a fix available, CVSS 8.2
Cross-site Scripting (XSS)
SNYK-PYTHON-LXML-2316995
lxml:
3.4.0 -> 4.9.1
No No Known Exploit
medium severity 586/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 5.3
NULL Pointer Dereference
SNYK-PYTHON-LXML-2940874
lxml:
3.4.0 -> 4.9.1
No Proof of Concept
medium severity 539/1000
Why? Has a fix available, CVSS 6.5
Cross-site Scripting (XSS)
SNYK-PYTHON-LXML-72651
lxml:
3.4.0 -> 4.9.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:

🦉 Cross-site Scripting (XSS)
🦉 Arbitrary File Write
🦉 Cross-site Scripting (XSS)
🦉 More lessons are available in Snyk Learn

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants