SecurityResearch-101

Web Services and API Penetration Testing Part #2 Welcome readers to Part 2 of Web Services Penetration Testing. In this part, we will take a quick look into the various test cases, tools and method for security testing of Web Services. Black box Web Services Penetration Testing pre-requisite: è Web Service Description Language (WSDL) file Grey box Web Services Penetration Testing pre-requisite: è Sample requests/responses for methods along with WSDL file. Stages of Penetration Testing of Web Service: 1.        Information Gathering 2.        Black Box 3.        Google hacking (using dorks to discover web services for websites hosted over network) 4.        UDDI 5.        Web Service Discovery (If no WSDL provided) 6.        Authentication Type Discovery Testing Methodology: è Automated Testing Tools ·          SoapUI Pro ·          OWASP ZAP ·          IBM AppScan ·          HP Webinspect ·          WSBang ·          WSMap è Manual

HTML Injection- October CMS By- Samrat Das Hi Readers, Recently while performing some open source security assessment, I came across an CMS Application, “October CMS” . Curious to explore its functionalities, I set up a local copy and started playing around to find security vulnerabilities’.   Title of the Vulnerability :   HTML Injection. Vulnerability Class : Code Execution/ Information Stealing Technical Details & Description : The application source code is coded in a way which allows malicious HTML commands to be executed in the inner pages which can lead to execution of arbitrary code. CVE ID allocated :  -   CVE-2018-7198 Product & Service Introduction : October CMS Steps to Re-Produce – 1.        Visit the application 2.        Visit the Add Posts Page. 3.          Goto edit function and add any html payload, it gets saved and executed further in web page. Exploitation Technique : A attacker can perform application defacing

Cross Site Request Forgery- Front Accounting ERP 2.4.3 By- Samrat Das Hi Readers, Recently while performing some open source security assessment, I came across an ERP Application- Front Accounting . Curious to explore its functionalities, I set up a local copy and started playing around to find security vulnerabilities’.   Title of the Vulnerability :   Cross Site Request Forgery. Vulnerability Class : Remote Code Execution/ Account takeover Technical Details & Description : The application source code is coded in a way which allows malicious crafted HTML page to be executed directly without any anti csrf countermeasures. CVE ID allocated :    CVE-2018-7176 Product & Service Introduction : Front Accounting 2.4.3 Steps to Re-Produce – 1.        Visit the application 2.        Visit the User Permissions Page. 3.          Goto add user, and create a csrf crafted exploit for the same , upon hosting it on a server and sending the link to cl