Conversation
The following vulnerabilities are fixed by pinning transitive dependencies: - https://snyk.io/vuln/SNYK-PYTHON-CRYPTOGRAPHY-6592767 - https://snyk.io/vuln/SNYK-PYTHON-DNSPYTHON-6241713 - https://snyk.io/vuln/SNYK-PYTHON-JINJA2-6809379
|
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
🚮 Removed packages: pypi/jpype1@1.5.0, pypi/jpype1@1.5.0, pypi/jpype1@1.5.0, pypi/jpype1@1.5.0, pypi/jpype1@1.5.0, pypi/jpype1@1.5.0, pypi/jpype1@1.5.0, pypi/jpype1@1.5.0, pypi/jpype1@1.5.0, pypi/jpype1@1.5.0, pypi/jpype1@1.5.0, pypi/jpype1@1.5.0, pypi/jpype1@1.5.0, pypi/jpype1@1.5.0, pypi/jpype1@1.5.0, pypi/jpype1@1.5.0, pypi/jpype1@1.5.0, pypi/json5@0.9.25, pypi/json5@0.9.25, pypi/jsonpath-ng@1.6.1, pypi/jsonpath-ng@1.6.1, pypi/jsonpath-rw@1.4.0, pypi/opensearch-py@2.4.2, pypi/opensearch-py@2.4.2, pypi/opensearch-py@2.5.0, pypi/opensearch-py@2.5.0, pypi/pymongo@4.7.2, pypi/pymongo@4.7.2, pypi/pymongo@4.7.2, pypi/pymongo@4.7.2, pypi/pymongo@4.7.2, pypi/pymongo@4.7.2 |
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
Vulnerabilities that will be fixed
By pinning:
Why? Confidentiality impact: None, Integrity impact: None, Availability impact: Low, Scope: Unchanged, Exploit Maturity: No data, User Interaction (UI): None, Privileges Required (PR): None, Attack Complexity: High, Attack Vector: Network, EPSS: 0.00044, Social Trends: No, Days since published: 32, Reachable: No, Transitive dependency: Yes, Is Malicious: No, Business Criticality: High, Provider Urgency: Low, Package Popularity Score: 99, Impact: 2.35, Likelihood: 1.84, Score Version: V5
SNYK-PYTHON-CRYPTOGRAPHY-6592767
cryptography:42.0.5 -> 42.0.6Why? Confidentiality impact: None, Integrity impact: None, Availability impact: High, Scope: Unchanged, Exploit Maturity: Proof of Concept, User Interaction (UI): None, Privileges Required (PR): None, Attack Complexity: High, Attack Vector: Network, EPSS: 0.00044, Social Trends: No, Days since published: 90, Reachable: No, Transitive dependency: Yes, Is Malicious: No, Business Criticality: High, Provider Urgency: Medium, Package Popularity Score: 99, Impact: 5.99, Likelihood: 2.59, Score Version: V5
SNYK-PYTHON-DNSPYTHON-6241713
dnspython:2.3.0 -> 2.6.1Why? Confidentiality impact: Low, Integrity impact: Low, Availability impact: None, Scope: Unchanged, Exploit Maturity: No data, User Interaction (UI): Required, Privileges Required (PR): None, Attack Complexity: Low, Attack Vector: Network, EPSS: 0.00043, Social Trends: No, Days since published: 4, Reachable: No, Transitive dependency: No, Is Malicious: No, Business Criticality: High, Provider Urgency: Medium, Package Popularity Score: 99, Impact: 4.19, Likelihood: 2.15, Score Version: V5
SNYK-PYTHON-JINJA2-6809379
jinja2:3.1.3 -> 3.1.4(*) 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:
🦉 Uncontrolled Resource Consumption ('Resource Exhaustion')
🦉 Cross-site Scripting (XSS)