Skip to content
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

Filter out email addresses in responses #32

Conversation

BugBountyzip
Copy link
Contributor

Bambda Contributions

  • Bambda has a valid header, featuring an @author annotation and suitable description
  • Bambda compiles and executes as expected
  • Only .bambda files have been added or modified (README.md files are automatically updated / generated after PR merge)

Update README file
fix the link
 The script is designed to efficiently parse through response data to identify and filter out email addresses. It begins by establishing a set of ignored file extensions, ensuring that the script does not process irrelevant response types such as images or multimedia files. The core functionality revolves around a regular expression that is meticulously crafted to detect email addresses within the response body, excluding specific file formats in the domain part of the email to enhance accuracy.
This code targets HTTP requests that use deprecated or less common methods, such as TRACE and CONNECT. These methods are often overlooked but can be exploited in certain types of network attacks. When such a request is detected, the script highlights it in red within the Burp Suite interface, making it easy for security analysts to spot and investigate these potentially risky requests.
 * This script identifies and highlights HTTP responses containing developer notes in HTML, JavaScript, or other files.

 * It differentiates the types of files and highlights them accordingly: green for HTML, yellow for JavaScript, and blue for other types.
This script is designed to enhance security assessments by identifying potentially hazardous JavaScript functions in web applications. It meticulously scans HTTP responses with a Content-Type of application/javascript and flags responses containing functions like eval(), setTimeout(), and document.write().. The script highlights such responses in red, drawing immediate attention, and adds concise notes specifying the detected functions.
@Hannah-PortSwigger
Copy link
Contributor

Thanks for making this submission! Unfortunately, we've run out of time to continue this review this week so we will provide feedback on your pull request on Monday.

@BugBountyzip
Copy link
Contributor Author

Thank you for the update. I understand how busy schedules can be, and I appreciate your attention to the review process. Please take the time you need to provide feedback on the pull requests. I'm here to assist with any further clarifications or adjustments as required once you've had the chance to review them.

Looking forward to your feedback. Have a great week!

Copy link
Collaborator

@PortSwiggerWiener PortSwiggerWiener left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for your patience during the review process.

Looks good 👍

@BugBountyzip
Copy link
Contributor Author

Thank you for the opportunity to contribute here. I'm proud to announce that I've become the #1 contributor on this GitHub repository.

Looking forward to sharing more in the future.

Copy link
Contributor

@ps-porpoise ps-porpoise left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 Looks good.

@PortSwiggerWiener PortSwiggerWiener merged commit ef9093f into PortSwigger:main Dec 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

4 participants