A blog to share knowledge across the world of cybersecurity including: Offensive security, Secure DevOps, Incident Response, Reverse Engineering and Emerging technologies
Feel free to navigate different articles on the left side panel to learn and expand cyber knowledge!
Feel free to connect with me over social media channels as well!
Cross Site Request Forgery- Intex Router N-150 | CVE-2018-12529
By- Navina Asrani
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
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 –
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
4.Upon the link
being clicked by a logged in admin user, immediately, the action will get
Exploitation Technique: A attacker can create a rogue admin
user to gain access to the application.
Severity Level: High
The presence of such a risk can lead to router compromise as well as privileged user access.
By- Samrat Das Hi Readers Recently in one of my pentest research, I found a CMS " WonderCMS" hosted in github. Curious to explore its functionalities, I downloaded and set it up in my local system. After fiddling with the source code, I found that it did not have any kind of file upload security mechanism and allowed the user to upload any file type! After reporting it to them, I did not receive any security relevant response, hence decided to publish a blog on this. Title of the Vulnerability: Arbitrary File Upload Vulnerability Class: Security Misconfiguration Technical Details & Description: The application source code is coded in a way which allows arbitrary file extensions to be uploaded. This leads to uploading of remote shells/ malicious Trojans which can lead to complete system compromise and server takeover. CVE ID allocated : CVE-2017-14521 Product & Service Introduction: Wonder CMS 2.3.1 WonderCMS is an open source CMS (Content Ma
A great matter of debate and confusion I have always seen is the line of difference between SOAR and SIEM along with fact that if you have one, do you still need the other or in conjunction. In order to understand the clarity, let us analyze the details and the concept behind both one by one: 1. Understanding SIEM SIEM is the abbreviation for the technology platforms which stands for security information and event management used to collect and store security data. This can be related to simple examples including firewalls, intrusion detection systems/ prevention systems etc. This technically helps to aggregate and correlate all of this gathered data by help in analyze date wth focused analytics and machine learning software. 2. Understanding SOAR SOAR on the other hand is the collective technology involving Security orchestration, automation and response (SOAR), that is intended to help imbibe security operations with the pillars of efficiency and consisten
After getting the basics of thick client pentest, let’s delve into the very first steps you can take to commence thick client pentest. Interception and setting up proxy of application. Thick clients can be broken down into two types based on proxy settings: 1 1) Proxy aware 2) Proxy unaware Proxy aware are those applications which has settings in the application itself to route through IP address and ports for the purpose of logging in the application as well as transmit and receive data. Whenever you log into the application, you will be given a prompt showing username/ password along with destination IP and port. In case where the application does not have such settings, and only accepts username and password for authentication, you have to redirect the traffic from the application to your system to the actual server. This is the case of proxy unaware thick clients. Let’s see how: The very first step involves in getting the hostname of the thick client applic