Skip to content
This repository was archived by the owner on Nov 15, 2024. It is now read-only.

[Snyk] Security upgrade lxml from 4.3.4 to 4.9.1#13

Open
violethaze74 wants to merge 1 commit intodevelopfrom
snyk-fix-9637139210167000e18d6f22c36f9ca5
Open

[Snyk] Security upgrade lxml from 4.3.4 to 4.9.1#13
violethaze74 wants to merge 1 commit intodevelopfrom
snyk-fix-9637139210167000e18d6f22c36f9ca5

Conversation

@violethaze74
Copy link

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:
    • dockstore-webservice/src/main/resources/requirements/1.7.0/requirements.txt
⚠️ Warning
prov 1.5.1 requires networkx, which is not installed.
cwltool 1.0.20190621234233 requires bagit, 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:
4.3.4 -> 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:
4.3.4 -> 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:
4.3.4 -> 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:
4.3.4 -> 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:
4.3.4 -> 4.9.1
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:

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

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