deprecated extender api used -registerMenultem()

[shyixiu]

When i installed blazer, the Alerts tab showed "Blazer:deprecated extender api used-registerMenultem()". And there is nothing happened after i click"Blazer - AMF testing".BTW,I used burp 1.7.30

[ikkisoft]

The alert shouldn't really affect the functionality, and it's just a warning. For instance, on Burp 1.3.72 enabling/disabling the sandbox works.

Please note that "Blazer - AMF testing" only works (e.g. will open the fuzzer interface) if there is an actual 'flex.messaging.messages.RemotingMessage' object in the HTTP request.

Are you sure that you're testing AMF-based remoting?
You should at least see an exception in std error "Does the request contain a valid 'flex.messaging.messages.RemotingMessage' ?!?"

[shyixiu]

Thanks for your replying. At first I used Burp_v1.7.30 and there was some error message in the extender tab. Then I switch to Burp 1.6 and it works properly.

[ikkisoft]

If you can provide the exception, I will take a look. The alert on the deprecated API shouldn't matter.

[shyixiu]

Here is the exception:

java.lang.NullPointerException
	at burp.CustomMenuItem.menuItemClicked(BurpExtender.java:151)
	at burp.naf.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)

[ikkisoft]

One more thing: can you send me the HTTP request/response that you're selecting when clicking on the menu item. You can use the export request/response feature of Burp. Thanks!

[shyixiu]

Ok, I sent you an email.

[sandeepl337]

Same issue with the latest Burp. is this project dead or anyone still can fix this issue.

[ikkisoft]

I am no longer maintaining the project. Time permitting, I will take a look but it may take months.

[ccsplit]

It appears the issue is caused by new Float(*) to obtain the current Burpsuite version. Especially within the current beta builds where getBurpVersion() returns Burp Suite, 2.0, 06beta.

Once I get a chance to properly test I will submit a PR if you don't end up resolving the issue.

[ikkisoft]

Thanks to @ccsplit - this is actually fixed in v0.3.2