I recently had cause to create a proof-of-concept for a site that seemed to be vulnerable to Cross-Site Request Forgery (CSRF).  I say "seemed" because there was no CSRF protection, but I was finding the XML POST body really hard to forge (It was a SOAP / XMLRPC type request).

Eventually Sid from notsosecure.com pointed me in the right direction.  The solution is not new, but it's interesting if you've never come across this problem before.

Version 1.1 of the Yaptest Frontend is now available.  Download it here.

 There are three main improvements to the interface:

• The "Ports" page now displays Nmap version and service information when it's available.
• The "Windows Info" page displays a list of Windows hosts along with various information about each: Domain name, whether the host is a domain controller, whether it's in a workgroup or a domain, its SID, password complexity setting and account lockout policy.
• The "Nessus" page simply display the nessus HTML report for the corresponding host.

Version 0.2.1 of yaptest is now available.  Download it here.

This is quite a major update.  The most notable improvements are support for running Nessus and/or OpenVAS.  At present Nessus and OpenVAS are automatically run against  any open ports with Safe Checks enabled.

As with any major update one or two bugs might have crept in.  Please mail pentestmonkey at pentestmonkey dot net if you find anything's broken.

The complete changelog is included below: