Skip to main content

Posts

Malicious File Upload- Intex Router N-150 | CVE-2018-12529

By- Samrat Das & Navina Asrani
Hi Readers,
Recently while tinkering with my wifi router, I was curious to find if it has possible loopholes and vulnerabilities. Curious to explore its functionalities, I started probing with the options.
Title of the Vulnerability:Malicious File Upload
Vulnerability Class: Firmware Compromise/ File Upload
Technical Details & Description: The firmware allows malicious files to be uploaded without any checking of extensions and allows filed to be uploaded.
CVE ID allocated: - CVE-2018-12528
Product & Service Introduction: InteX Router
Steps to Re-Produce – 1.Visit the application 2.Go to the advanced settings post login 3.Under backup- restore page upload any random file extension and hit go. 4.Upon the file being upload, the firmware will get rebooted accepting the arbitrary file. Exploitation Technique: A attacker can upload malicious files to compromise the firmware. Severity Level: High Security Risk: The presence of such a risk can le…
Recent posts

Cross Site Request Forgery- Intex Router N-150 | CVE-2018-12529

By- Samrat Das & Navina Asrani
Hi Readers,
Recently while tinkering with my wifi router, I was curious to find if it has possible loopholes and vulnerabilities. Curious to explore its functionalities, I started probing with the options.
Title of the Vulnerability:Cross Site Request Forgery
Vulnerability Class: Code Execution/ Privilege Escalation
Technical Details & Description: The firmware allows malicious request to be executed without verifying source of request. This leads to arbitrary execution with malicious request which will lead to the creation of a privileged user.
CVE ID allocated: -  CVE-2018-12529
Product & Service Introduction: Intex Router
Steps to Re-Produce – 1.Visit the application 2.Go to any router setting modification page and change the values, create a request and observe the lack of CSRF tokens. 3.Craft an html page with all the details for the built-in admin user creation and host it on a server 4.Upon the link being clicked by a logged in admin …

Cross Site Request Forgery- Frog CMS CVE ID : CVE-2018-8908

Cross Site Request Forgery- Frog CMS

By- Samrat Das

Hi Readers,

Recently while performing some open source security assessment, I came across an CMS Application, “Frog CMS” . 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: Code Execution/ Privilege Escalation

Technical Details & Description: The application source code is coded in a way which allows malicious HTML request to be executed without veryifying source of request.This leads to arbitary execution with malicous request which will lead to the creation of a privileged user.

CVE ID allocated: -  CVE-2018-8908


Product & Service Introduction: Frog CMS

Steps to Re-Produce
1.       Visit the application
2.       Visit the Add Users Page.
3.       Craft an html page with all the details for an admin user creation and host it on a server
4.       Upon the link being clicked by a l…

What are the initial steps to become a hacker?

As all say, the basics are what takes you ahead!

For being a hacker ( a real one)

1. Learn programming ! ( its not an option, rather a must)

Learning to make your own tools is a must for a hacker, start with learning C/ Python. Upon advancing get hands dirty with Ruby/ Perl. These will help you make scripts to automate attacks and create tools.

Reason:  Being a hacker means building your own tools to automate attacks, fuzz through input fields and create tools customized for different environments according to scenario.

Once you are adept at this, learn at least one server side language ( preferably PHP, otherwise JSP/ ASP)

At a glance, the languages you need to be good at least in basics:

1) C Programming ( for low level attacks such as buffer overflow/ memory attacks)
2) Java Programming ( helps code quickly tools for security testing)
3) Powershell ( much needed for exploitation on Windows and Red Teaming attacks)
4) Python ( a much hand scripting language needed for automating scr…

Web Services/ API Penetration Testing Part - 2

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 Testing Tools ·Soap UI Free ·Burp Suite Pro ·Postman ( with burp) èExtensions: ·SAML Editor ·SAML Encoder / Decoder

HTML Injection- October CMS - CVE-2018-7198

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 to information stealing.
Severity Level: High
Security Risk: The presence of such a risk ca…

Cross Site Request Forgery- Front Accounting ERP 2.4.3 - CVE-2018-7176

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 click by victim, it gets exploited. Exploitation Technique: A attacker can perform applica…