Research Academy
My account Customers About Blog Careers Legal Contact Resellers
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

Base64 decode in HTTP history tab

| Last updated: Oct 29, 2021 09:54AM UTC

With the latest version (2021.9.1) it's no more possible to decode base64 in the HTTP history tab using ctrl + shift + b. This problem is also present in the intercept tab

Uthman, PortSwigger Agent | Last updated: Oct 29, 2021 12:37PM UTC

Hi,

Thanks for reporting this!

I've raised a bug with our development team and this thread will be updated when the issue has been fixed.

Out of curiosity, is the issue only occurring for base64 strings with padding? Can you decode properly if you highlight the string without padding? E.g. If aGVsbG8gdGhpcyBpcyBhIHRlc3Q%3D was our starting string, aGVsbG8gdGhpcyBpcyBhIHRlc3Q would be highlighted before the hotkey is invoked.

If you decode aGVsbG8gdGhpcyBpcyBhIHRlc3Q= in the Repeater without the URL encoded =, does it work?

| Last updated: Oct 29, 2021 01:09PM UTC

With the string provided the decode works fine, but with an other strings (for example a JWT token) it's not possible to decode. At the moment seems to work only the encoding

Uthman, PortSwigger Agent | Last updated: Oct 29, 2021 01:12PM UTC