This repository has been archived by the owner on Dec 3, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 170
[Snyk] Security upgrade urllib3 from 1.23 to 1.26.18 #246
Open
sscottgvit
wants to merge
540
commits into
master
Choose a base branch
from
snyk-fix-7ceb0d561e74c99a6706669825c90428
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Changed links to govanguard.com, added Keybase team link.
- Addresses github issue #18
Fix complex predicate bug
Update README typos and line wrapping
Merge latest dev into master
- Ran ui/eventfilter.py through CodeClimate CLI and is no longer showing any cognitive complexity issues in the logic
- The file was not loaded correctly by Legion on startup due to an error with a trailing single quote
- This commit is the 2nd iteration on reducing complexity of `logic.py` - Introduces the concept of a repository. A repository is an abstraction on a data store. In the case of Legion, the underlying data store is based on SQLite, and so the repository implementations should contain all SQL code within the app. - There is a repository for each concept within the app, such as a Process, a Service, a Host, a Port, etc. (e.g. ProcessRepository, HostRepository, etc.) - This commit does not complete the full refactoring of all SQL related code to a repository. Further commits will be added to complete the work. - All new code added was driven by an underlying unit test. In order to gain confidence in proper refactoring of existing logic, a backporting of unit tests was needed.
Fix complexity bug in eventfilter
Adding instructions to modify scan configurations
Update README.md
Added Cutycapt --insecure flag to ignore SSL/TLS certificate errors
…sh-1 Fix updateProgress to always use an integer
fix bad interpreter: /bin/bash^M: no such file or directory
Removed old dead links.
The following vulnerabilities are fixed by pinning transitive dependencies: - https://snyk.io/vuln/SNYK-PYTHON-URLLIB3-1014645 - https://snyk.io/vuln/SNYK-PYTHON-URLLIB3-1533435 - https://snyk.io/vuln/SNYK-PYTHON-URLLIB3-174323 - https://snyk.io/vuln/SNYK-PYTHON-URLLIB3-174464 - https://snyk.io/vuln/SNYK-PYTHON-URLLIB3-5926907 - https://snyk.io/vuln/SNYK-PYTHON-URLLIB3-5969479 - https://snyk.io/vuln/SNYK-PYTHON-URLLIB3-6002459
sscottgvit
force-pushed
the
master
branch
3 times, most recently
from
November 4, 2024 18:10
35e18d0
to
ea40ce5
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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:
SNYK-PYTHON-URLLIB3-1014645
urllib3:
1.23 -> 1.26.18
SNYK-PYTHON-URLLIB3-1533435
urllib3:
1.23 -> 1.26.18
SNYK-PYTHON-URLLIB3-174323
urllib3:
1.23 -> 1.26.18
SNYK-PYTHON-URLLIB3-174464
urllib3:
1.23 -> 1.26.18
SNYK-PYTHON-URLLIB3-5926907
urllib3:
1.23 -> 1.26.18
SNYK-PYTHON-URLLIB3-5969479
urllib3:
1.23 -> 1.26.18
SNYK-PYTHON-URLLIB3-6002459
urllib3:
1.23 -> 1.26.18
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:
🦉 Regular Expression Denial of Service (ReDoS)
🦉 CRLF injection