secure-code-warrior-for-github[bot]
commented
1 year ago Micro-Learning Topic: External entity injection (Detected by phrase)
Matched on "XXE"
An XML External Entity attack is a type of attack against an application that parses XML input. This attack occurs when XML input containing a reference to an external entity is processed by a weakly configured XML parser. This attack may lead to the disclosure of confidential data, denial of service, server-side request forgery, port scanning from the perspective of the machine where the parser is located, and other system impacts.
Try a challenge in Secure Code Warrior
Helpful references
- OWASP XML External Entity (XXE) Processing - OWASP community page with comprehensive information about XML external entity attacks, and links to various OWASP resources to help detect or prevent it.
- MSDN Security Briefs - XML Denial of Service Attacks and Defenses - An MSDN Magazine article that goes into detail on XML entity attacks and how to defend against them.
- OWASP XML External Entity Prevention Cheat Sheet - This article is focused on providing clear, simple, actionable guidance for preventing XML external entity flaws in your applications.
pull-request-quantifier-deprecated[bot]
performance-testing-bot[bot]
senior-dev-bot[bot]
difflens[bot]
viezly[bot]
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.txt⚠️ Warning
``` transformers 4.30.2 has requirement tokenizers!=0.11.3,<0.14,>=0.11.1, but you have tokenizers 0.15.0. torch 1.13.1 requires nvidia-cuda-runtime-cu11, which is not installed. torch 1.13.1 requires nvidia-cublas-cu11, which is not installed. torch 1.13.1 requires nvidia-cuda-nvrtc-cu11, which is not installed. torch 1.13.1 requires nvidia-cudnn-cu11, which is not installed. tensorboard 2.11.2 has requirement protobuf<4,>=3.9.2, but you have protobuf 4.24.4. tensorboard 2.11.2 has requirement setuptools>=41.0.0, but you have setuptools 39.0.1. scikit-learn 1.0.2 requires scipy, which is not installed. python-igraph 0.11.3 has requirement igraph==0.11.3, but you have igraph 0.10.8. powerlaw 1.5 requires scipy, which is not installed. pipenv 2023.10.3 has requirement setuptools>=67, but you have setuptools 39.0.1. paddlenlp 2.6.1 requires seqeval, which is not installed. paddlenlp 2.6.1 has requirement protobuf==3.20.2, but you have protobuf 4.24.4. paddlenlp 2.6.1 has requirement dill<0.3.5, but you have dill 0.3.7. paddlenlp 2.6.1 has requirement multiprocess<=0.70.12.2, but you have multiprocess 0.70.15. paddle2onnx 0.9.5 has requirement onnx<=1.9.0, but you have onnx 1.14.1. onnxruntime 1.14.1 requires sympy, which is not installed. onnxruntime 1.14.1 has requirement numpy>=1.21.6, but you have numpy 1.21.3. onnxruntime-gpu 1.14.1 requires sympy, which is not installed. onnxruntime-gpu 1.14.1 has requirement numpy>=1.21.6, but you have numpy 1.21.3. lpips 0.1.4 requires scipy, which is not installed. filterpy 1.4.5 requires scipy, which is not installed. facexlib 0.3.0 requires scipy, which is not installed. datasets 2.13.2 has requirement dill<0.3.7,>=0.3.0, but you have dill 0.3.7. botocore 1.32.6 has requirement urllib3<1.27,>=1.25.4; python_version < "3.10", but you have urllib3 2.0.7. ```**Why?** Recently disclosed, Has a fix available, CVSS 7.3 | XML External Entity (XXE) Injection
[SNYK-PYTHON-SYMPY-6084333](https://snyk.io/vuln/SNYK-PYTHON-SYMPY-6084333) | `sympy:`
`1.10.1 -> 1.12`
| 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: