Research Academy
My account Customers About Blog Careers Legal Contact Resellers

Burp Suite User Forum

Create new post

Possible Classpath Issues when using beansbinding (JSR 295)

D | Last updated: Mar 24, 2017 10:14AM UTC

Hi everyone I am currently trying to finalize my Burp Suite extension. To bind POJOs to the View (two-way binding) I am using beansbinding respectively betterbeansbinding (JSR 295). When I start my extension via NetBeans or load the extension via classpath (Legacy Java) everything works fine. When I load it via the Burp Suite Extender the two-way binding does not work anymore. I would really love to use this feature due to the good support when using NetBeans. Do you guys have any idea what makes the difference here? I am pretty sure, that my code is correct, I have been successfully using this feature since years. Thank you very much for your help!

PortSwigger Agent | Last updated: Mar 24, 2017 11:30AM UTC

Each extension (other than a legacy extension loaded from the classpath) runs in its own sandboxed classloader, to prevent naming collisions between classes used by extensions. It's possible that this segregation is causing the issue you are seeing, and if so you might be able to come up with a workaround in your code based on that information.

Burp User | Last updated: Mar 24, 2017 12:27PM UTC

Thank you for your answer. Currently I have no idea where to start. I am wondering if someone ever created a running two-way binding using JSR 295 (beansbinding or betterbeansbinding). How are you performing two-way bindings within Burp Suite? Do you have a curated list of known "problematic" dependencies?

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