Research Academy
My account Customers About Blog Careers Legal Contact Resellers

Burp Suite User Forum

Create new post

AMF decoding applied to requests only

Nicolas | Last updated: Dec 05, 2017 03:51PM UTC

Hello, I'm using Burp to proxy some traffic to an AMF gateway. Both requests and responses have the "Content-Type: application/x-amf" header. However, only requests are AMF-decoded . Of course, option "User Options / HTTP Message Display / Analyze and display AMF messages" is set. Any ideas? Additionally, the Blazer extension crashes with a NPE, but I known that's not your problem ;-) Thanks in advance, Nicolas

Burp User | Last updated: Dec 05, 2017 03:51PM UTC

Looks similar to https://support.portswigger.net/customer/portal/questions/16996396-issue-deserializing-amf-messages-with-burpsuite

PortSwigger Agent | Last updated: Dec 08, 2017 02:07PM UTC

Hi Nicolas, Thanks for your message. AMF decoding is working for both requests and responses on this site: http://census2.jamesward.com/ Does that work for you as well? The AMF tab will only appear if it can deserialize the message. That suggests there's something in your responses that we can't parse. Would you be able to share an example response? There are some extensions for AMF - AMF Deserializer and BurpAMFDSer. We'd be interested to know if you have more success with them. Please let us know if you need any further assistance.

You must be an existing, logged-in customer to reply to a thread. Please email us for additional support.