The Burp Suite User Forum was discontinued on the 1st November 2024.

Burp Suite User Forum

For support requests, go to the Support Center. To discuss with other Burp users, head to our Discord page.

SUPPORT CENTER DISCORD

Higher unicode characters mangled when pasting

Serge | Last updated: Sep 30, 2015 12:37PM UTC

When pasting text into Burp Suite, with the text containing unicode characters with a codepoint higher than 255, Burp Suite will mangle the characters. For characters with a unicode code point lower than 65536, the result is that the higher byte of each code point is discarded. To reproduce: * select the following text and copy it to the clipboard: ntUUuGruUUTg * in Burp Suite, paste the text in the repeater. * The text 'Hello World!' will appear. This bug relates at least to Burp Suite Free Edition 1.6.25 on Ubuntu 14.04.02.

Burp User | Last updated: Sep 30, 2015 02:34PM UTC

Additionally, if you actually manage to enter text with higher codepoint unicode characters in the 'raw' tab — for instance through 'paste from file' — then the text is displayed incorrectly in the 'params' tab.

PortSwigger Agent | Last updated: Oct 02, 2015 08:02AM UTC

Are you trying to put high Unicode characters into a request? This raises some issues because HTTP requests can only contain raw bytes for transmission across the wire. Normally, if you want to represent a high Unicode character within a request, you would URL-encode it using a multi-byte sequence. If you are in a context where a specific content type and character set has been defined (e.g. in an HTTP response body), you could represent high Unicode bytes using the raw byte sequences applicable for the chosen character set. But this is not normally the case - typically, during testing, you will be modifying requests and you need to represent high characters in a URL-encoded form.

Burp User | Last updated: Oct 31, 2015 07:37PM UTC

It's all down to the encoding of the request, and the bit of the request you want to put it in, no? The headers are AFAIK old-school ASCII only. You might be able to shoe horn other stuff into it, but it's not as per standard, and whether anything responds is totally implementation dependent. Always fun to try though. ;) The body is a totally different matter and down to the content-type (and charset) of the request. text/html; charset=utf-8 is totally valid for a request, so unicode, multibyte characters can and should be expected!

PortSwigger Agent | Last updated: Nov 02, 2015 09:52AM UTC

This isn't resolved in core Burp, although this extension may help you: - https://github.com/pajswigger/utf8-message-editor

Burp User | Last updated: Dec 13, 2018 01:32PM UTC