XSS character encoding artifact (chrome plug-in)

XSS character encoding artifact (chrome plug-in) is an excellent plug-in in browsers with chrome as the core. It can help users solve browser XSS character encoding problems. The plug-in integrates HTML, JS, Base6, UTF-7, etc. Encoding, users in need can download it with confidence.

Instructions for use:

1. After the installation is complete, open the chrome browser console (F12), and you will see XSS Encode! Click to see the main interface!

2. Encoding: Put the content to be processed in the text field on the left, click the drop-down box next to encoding to select the encoding function you want to use, and then click the encoding button, and the processed result will be output in the text field on the right. content.

3. Decoding: Put the encoding to be processed in the text field on the left, click the drop-down box next to decoding to select the decoding function you want to use, and then click decode, and the processed code will be output in the text field on the right. content.

4. The function of regular variation of Hex coding: it will add 7 more 0s to the number in front of the code, because IE adds 0 to the hex coding and only recognizes eight 0s. If there are more, it will be considered as not a valid value! There are also Many program filtering rules are written like this! They will parse your mutated value back and then determine whether it is a dangerous character!

Applicable scenario: When the hexadecimal encoding is parsed back and filtered again, for example, < is restored in the filter program and filtered again! However, < is not restored in the filter program, but is parsed by the browser on the page. Restored, then you can use the conventional mutation of hexadecimal encoding!

5. Unconventional mutation function of Hex encoding: 10 more zeros will be added in front of the encoded number! The reason is the same as above!

Applicable scenario: When the hexadecimal encoding is parsed back and filtered again, such as < or ? are restored and filtered again, then unconventional mutations can be used! IE recognizes 8 0s, but Chrome can recognize more Too many 0s! Some filtering mechanisms are written based on the 8 0s of IE! So more 0s are also a way to bypass it!

HTML encoding to remove semicolons: Semicolons can be removed, which can save you more characters. (This option can be used in conjunction with other options. For example, when encoding HTML, check the regular mutation + remove the semicolon from HTML encoding)

6. Payload URL encoding: &# has special meaning in the URL. We often regard them as a representation of HTML entity encoding! But the browser does not think so, & will be considered as the parameter separator. , the # sign is the value obtained by location.hash and so on. It will not be sent to the server. If it is reflected XSS or the like, then check it!

7. UTF-7 encoding: I won’t explain this. There have been a lot of UTF-7 XSS before and you will understand after taking a look!

8.UTF-8Jp: This encoding is also known as cute characters. The advantage is that it can bypass most blacklist filters, but the disadvantage is that there are too many characters!

9. After this plug-in discovers that the httponly Cookie is leaked, the default reminder method is Alert. If you often alert during normal Internet surfing, you can click to change the settings in the plug-in and select Close Alert.