Fix crash when DNSdumpster CSRF token is missing - #399
Open
TheSpidyOps wants to merge 1 commit into
Open
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Problem:
Sublist3r currently crashes when the DNSdumpster module fails to extract the CSRF token. This happens when DNSdumpster changes its HTML structure or blocks automated requests, resulting in an empty regex match. The script then throws an IndexError when it tries to access the first element of an empty list.
Fix:
Added a check to ensure that the CSRF token was successfully extracted before accessing it. If the token is missing, the script logs a warning and gracefully skips the DNSdumpster module instead of crashing.
This improves the stability and user experience of Sublist3r.