-
Notifications
You must be signed in to change notification settings - Fork 1.6k
♻️ Remove async import #12042
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
base: dev
Are you sure you want to change the base?
♻️ Remove async import #12042
Conversation
DryRun Security SummaryThe pull request removes deprecated asynchronous finding import features across multiple files, reducing security risks and simplifying system configuration by eliminating experimental code paths and potential concurrency-related vulnerabilities. Expand for full summaryPR Summary: Removal of deprecated asynchronous finding import feature across multiple files, including documentation updates, code cleanup in importers, and configuration settings modifications. Security Findings:
No direct security vulnerabilities were introduced by these changes. Code AnalysisWe ran
Overall Riskiness🔴 Risk threshold exceeded. We've notified @mtesauro, @grendel513. |
Can I suggest to change the title to "Remove async import"? |
Done |
@manuel-sommer thank you for doing this! It will definitely save us some time in the future. We are planning to remove this functionality in the June release to provide folks enough awareness and time. The earliest we could merge this would be shortly after the May release |
Sure, feel free to merge it later. :-) |
This pull request has conflicts, please resolve those before we can evaluate the pull request. |
I will resolve the conflicts once this will be picked up again. |
Conflicts have been resolved. A maintainer will review the pull request shortly. |
🔴 Risk threshold exceeded.This pull request involves sensitive edits to multiple importer files in the dojo/importers directory, with potential implications including reduced async processing capabilities, simplified code structure, and changes to import workflows that may impact performance and user configurations.
|
Vulnerability | Configured Codepaths Edit |
---|---|
Description | Sensitive edits detected for this file. Sensitive file paths and allowed authors can be configured in .dryrunsecurity.yaml . |
⚠️ Configured Codepaths Edit in dojo/importers/default_importer.py
Vulnerability | Configured Codepaths Edit |
---|---|
Description | Sensitive edits detected for this file. Sensitive file paths and allowed authors can be configured in .dryrunsecurity.yaml . |
⚠️ Configured Codepaths Edit in dojo/importers/default_reimporter.py
Vulnerability | Configured Codepaths Edit |
---|---|
Description | Sensitive edits detected for this file. Sensitive file paths and allowed authors can be configured in .dryrunsecurity.yaml . |
⚠️ Configured Codepaths Edit in dojo/importers/endpoint_manager.py
Vulnerability | Configured Codepaths Edit |
---|---|
Description | Sensitive edits detected for this file. Sensitive file paths and allowed authors can be configured in .dryrunsecurity.yaml . |
⚠️ Configured Codepaths Edit in dojo/importers/endpoint_manager.py
Vulnerability | Configured Codepaths Edit |
---|---|
Description | Sensitive edits detected for this file. Sensitive file paths and allowed authors can be configured in .dryrunsecurity.yaml . |
⚠️ Configured Codepaths Edit in dojo/importers/endpoint_manager.py
Vulnerability | Configured Codepaths Edit |
---|---|
Description | Sensitive edits detected for this file. Sensitive file paths and allowed authors can be configured in .dryrunsecurity.yaml . |
⚠️ Configured Codepaths Edit in dojo/importers/endpoint_manager.py
Vulnerability | Configured Codepaths Edit |
---|---|
Description | Sensitive edits detected for this file. Sensitive file paths and allowed authors can be configured in .dryrunsecurity.yaml . |
⚠️ Configured Codepaths Edit in dojo/importers/base_importer.py
Vulnerability | Configured Codepaths Edit |
---|---|
Description | Sensitive edits detected for this file. Sensitive file paths and allowed authors can be configured in .dryrunsecurity.yaml . |
⚠️ Configured Codepaths Edit in dojo/importers/default_importer.py
Vulnerability | Configured Codepaths Edit |
---|---|
Description | Sensitive edits detected for this file. Sensitive file paths and allowed authors can be configured in .dryrunsecurity.yaml . |
⚠️ Configured Codepaths Edit in dojo/importers/default_reimporter.py
Vulnerability | Configured Codepaths Edit |
---|---|
Description | Sensitive edits detected for this file. Sensitive file paths and allowed authors can be configured in .dryrunsecurity.yaml . |
💭 Unconfirmed Findings (5)
Vulnerability | Potential Information Disclosure |
---|---|
Description | Removal of documentation sections might reduce transparency about import mechanisms, potentially leaving users unaware of feature changes without consulting release notes. |
Vulnerability | Configuration Variable Removal |
---|---|
Description | Deprecated configuration variables related to async finding imports were removed, which could impact existing import workflows and processing strategies. |
Vulnerability | Reduced Attack Surface |
---|---|
Description | Eliminating async processing methods reduces risks such as race conditions, concurrency-related vulnerabilities, and potential experimental feature exploits. |
Vulnerability | Import and Code Cleanup |
---|---|
Description | Removing unused imports slightly decreases potential attack surface and simplifies the codebase, making it easier to audit and secure. |
Vulnerability | Potential Performance Considerations |
---|---|
Description | Switching to synchronous processing might negatively impact performance for large imports and could require users to modify their existing import strategies. |
We've notified @mtesauro.
All finding details can be found in the DryRun Security Dashboard.
TODO: Add a note for the release where this gets merged.