Wsdler icon indicating copy to clipboard operation
Wsdler copied to clipboard

Published 20 hours ago • verified publisher icon NetSPI

Not a WSDL

Open riramar opened this issue 8 years ago • 9 comments

Just installed Wsdler from BApp Store and following the steps from here https://blog.netspi.com/hacking-web-services-with-burp/ I'm always getting the "Parsing WSDL" and after that the error "Not a WSDL". The same WSDL can be parsed by SoapUI without any problem. Is there a log or debug mode?

riramar avatar Aug 12 '16 19:08 riramar

What's the MIME type on the WSDL response? It will only parse the WSDL if it's XML.

egru avatar Aug 12 '16 23:08 egru

I'll check and let you know.

riramar avatar Aug 15 '16 02:08 riramar

You're right. The server is returning "Content-Type: text/html;charset=UTF-8". I'm not the system admin neither a developer for this system. Can I change this header and ask Wsdler to parse?

riramar avatar Aug 15 '16 12:08 riramar

I gave a try but it didn't work. Just changed to "Content-Type: text/xml" but when I tried to parse from edited response on the Burp History I got the same error.

riramar avatar Aug 15 '16 13:08 riramar

I created a new jar that removes the MIME check. You can grab it here: https://github.com/NetSPI/Wsdler/releases/tag/2.0.11.1

egru avatar Aug 15 '16 14:08 egru

It worked! :) Thanks!

riramar avatar Aug 15 '16 14:08 riramar

Hi,

I added wsdlr version 2.0.11 from extensions, however wsdler is not parsing the wsdl file. Do i have to run via command line?

SOAP UI is parsing the wsdl without any issues.

prvnkumark avatar Jul 26 '17 08:07 prvnkumark

I'll take a look at it. The MIME check is removed from the initial look at the response, but there could be a issue further down in the parsing libraries. Is there any other error message that you're getting?

egru avatar Jul 31 '17 15:07 egru

Hi,

I am not getting any other error message, have you got chance to look into it?

prvnkumark avatar Aug 29 '17 11:08 prvnkumark