permalink: /Web_Service_Security_Testing_Cheat_Sheet/

__NOTOC__

{\| style=”padding: 0;margin:0;margin-top:10px;text-align:left;” \|- \| valign=”top” style=”border-right: 1px dotted gray;padding-right:25px;” \|
Last revision (mm/dd/yy): //

__TOC__

Web Services Security Testing Cheat Sheet Introduction

As Web Services are incorporated into application environments, having a good checklist while performing security assessments can help a penetration tester better identify web service related vulnerabilities and associated risk.

Purpose

This document is intended to be an easy to use checklist while performing assessments against web services. The penetration tester is advised to incorporate this into his or her corporate testing methodology as a supplemental checklist or is free to use this checklist as the sole testing guideline.

Checklist

Pre-Assessment

For a Black Box assessment, at the very least, the penetration tester will need the Web Service Description Language (WSDL) file
For a Grey Box assessment, the penetration tester will need sample requests for each method employed by the web service(s), along with the Web Service Description Language (WSDL) file

Information Gathering

Black Box
* Google hacking
** Inurl:jws?wsdl
** Inurl:asmx?wsdl
** Inurl:aspx?wsdl
** Inurl:ascx?wsdl
** Inurl:ashx?wsdl
** Inurl:dll?wsdl
** Inurl:exe?wsdl
** Inurl:php?wsdl
** Inurl:pl?wsdl
** Inurl:?wsdl
** Filetype:jws
** Filetype:asmx
** Filetype:ascx
** Filetype:aspx
** Filetype:ashx
** Filetype:dll
** Filetype:exe
** Filetype:php
** Filetype:pl
* WSDL file contents
** Methods
** Data Types
* UDDI
** Web Service Discovery (If no WSDL provided)
* Authentication Type Discovery
* REST vs. SOAP
* Baseline Requests
Grey Box
* WSDL file contents
** Methods
** Data Types
* Sample/Baseline Requests
** Methods
** Data Types
** Types of Information Being Requested/Consumed
* Authentication Type Discovery
* REST vs. SOAP

Testing Phase

Baseline Tests
* Normal Request(s)/Response(s) for Each Method
Automated Tests
* Tools
** SoapUI Pro
** OWASP ZAP
** IBM AppScan
** HP Webinspect
** WSBang
** WSMap
Vulnerability Discovery
* Debug output
* Fuzzing
* XSS
* SQLi
* Malformed XML
* Malicious Attachment/File Upload
* Xpath Injection
* Improper Boundary Checking
* XML Bomb (DoS)
* Basic Authentication
* SAML/OAuth/OpenID authentication
** Authentication based attacks
*** Replay attacks
*** Session fixation
*** XML Signature wrapping
*** Inadequate session timeout settings
** Improper implementation
* SSL/TLS Use
* Host Cipher Support
* Valid Certificate
* Protocol Support
* Hashing Algorithm Support
* Deprecated cipher suites that are offered
** External resources
*** SSL Labs
** Internal resources
*** SSLscan
*Authorization Bypass
* Schema Implementation Weaknesses
* Non-encoded Output
Manual Tests
* Tools
** Soap UI Free
** Burp Suite Pro
*** Suggested extensions:
**** SAML Editor
**** SAML Encoder / Decoder
**** WSDL Wizard
**** Wsdler
** SOA Client
** WSDigger (deprecated)
* Vulnerability Discovery
** Debug output
* Fuzzing
** XSS
** SQLi
** Malformed XML
** Malicious Attachment/File Upload
** Xpath Injection
** Improper Boundary Checking
** XML Bomb (DoS)
** Basic Authentication
** SSL/TLS Fallback

Testing REST Based Web Services

There is already a great cheat sheet on how to properly test the security of REST based web services. You can find the guide at the following location:
1 https://www.owasp.org/index.php/REST_Assessment_Cheat_Sheet

Testing Summary

While using automated tools, the penetration tester will need to validate all reported findings manually and perform due diligence false positive analysis for each vulnerability reported. During the manual phase of testing, the penetration tester will look for the existence of vulnerabilities missed by the automated tools and will validate automated tool output as necessary.