exploit the possibilities
Home Files News &[SERVICES_TAB]About Contact Add New

Yahoo! Flickr API Cross Site Scripting

Yahoo! Flickr API Cross Site Scripting
Posted Jul 7, 2014
Authored by Ateeq ur Rehman Khan, Vulnerability Laboratory | Site vulnerability-lab.com

The Yahoo! Flickr API suffered from a cross site scripting vulnerability.

tags | exploit, xss
SHA-256 | 0a82633363f77300f20ae19f62cd3f4f98f06a8fc9e22d76720d61fa71d3f3f1

Yahoo! Flickr API Cross Site Scripting

Change Mirror Download
Document Title:
Yahoo! Bug Bounty #25 Flickr API - Persistent Vulnerability

References (Source):

Release Date:

Vulnerability Laboratory ID (VL-ID):

Common Vulnerability Scoring System:

Product & Service Introduction:
Flickr is an image hosting and video hosting website, and web services suite that was created by Ludicorp in 2004 and acquired by Yahoo 2005.
In addition to being a popular website for users to share and embed personal photographs, and effectively an online community, the service is
widely used by photo researchers and by bloggers to host images that they embed in blogs and social media.

The Verge reported in March 2013 that Flickr had a total of 87 million registered members and more than 3.5 million new images uploaded daily.
In August 2011 the site reported that it was hosting more than 6 billion images and this number continues to grow steadily according to
reporting sources. Photos and videos can be accessed from Flickr without the need to register an account but an account must be made in order
to upload content onto the website. Registering an account also allows users to create a profile page containing photos and videos that the
user has uploaded and also grants the ability to add another Flickr user as a contact. For mobile users, Flickr has official mobile apps for
iOS, Android, PlayStation Vita, and Windows Phone operating systems.

(Copy of the Homepage: http://en.wikipedia.org/wiki/Flickr )

Abstract Advisory Information:
The Vulnerability Laboratory Research team discovered a persistent input validation web vulnerability in the official Yahoo Flickr! website web-application and api.

Vulnerability Disclosure Timeline:
2013-11-03: Researcher Notification & Coordination (Ateeq ur Rehman Khan - Vulnerability Lab)
2013-11-04: Vendor Notification (Yahoo! Security Team - Bug Bounty Program)
2014-01-09: Vendor Response/Feedback (Yahoo! Security Team - Bug Bounty Program)
2014-06-22: Vendor Fix/Patch (Yahoo! Developer Team - HackerOne Reward: 1000$)
2014-07-06: Public Disclosure (Vulnerability Laboratory)

Discovery Status:

Affected Product(s):
Product: Flickr Web Application - YPL API 2013 Q3

Exploitation Technique:

Severity Level:

Technical Details & Description:
A persistent input validation vulnerability has been discovered in the official Yahoo Flickr! website web-application and api.
The vulnerability allows remote attackers to inject own malicious script codes to the application-side of the online-service.

The vulnerability is located in the flickr `invite` mail notification module. Remote attackers are able to inject payloads to
the `message` value of the web-application notification service after the registration. The remote attacker can send invitation
mails through the yahoo online-service module with manipulated message body context. The attack vector of the issue is located
on the application-side and the request method to inject own malicious codes is POST.

The security risk of the persistent remote web vulnerability is estimated as medium with a cvss (common vulnerability scoring
system) count of 4.1. Exploitation of the vulnerability requires low user interaction and a low privileged flickr web-application
user account. Successful exploitation of the vulnerability result in session hijacking (customers), account steal via persistent
web attack (mail), persistent phishing or persistent manipulation of notification mails module context.

Vulnerable Service(s):
[+] Yahoo! > Flickr

Vulnerable Module(s):
[+] Invite (Invitation of Users)

Vulnerable Module(s):
[+] Notification Service (eMails)

Vulnerable Parameter(s):
[+] message (body)

Proof of Concept (PoC):
The persistent input validation web vulnerability can be exploited by remote attackers with low privileged yahoo web application user account
and low user interaction. For demonstration or to reproduce the security vulnerability follow the provided information and steps below to continue.

PoC: Flickr Message - Invitation Attachment > Message Body

<tr style="mso-yfti-irow:1">
<td style="padding:1.5pt 1.5pt 1.5pt 1.5pt">
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif""> <o:p></o:p></span></p>
<tr style="mso-yfti-irow:2">
<td style="border:solid #CCCCCC 1.0pt;mso-border-alt:solid #CCCCCC .75pt;
padding:7.5pt 7.5pt 7.5pt 7.5pt">
<p class="MsoNormal" style="line-height:13.5pt"><span style="font-size:
10.0pt;font-family:"Arial","sans-serif"">I want to share my Flickr
photostream with you. If you get bored of that, there's loads of other
things to see there too. '%3d[PERSISTENT INJECTED SCRIPT CODE VIA MESSAGE VALUE!!!]'>"><b><span style="color:#E83DA6">free</span></b>
and takes less than a minute with your Yahoo! ID.<o:p></o:p></span></p>

Note: pTest:> bugbountyevo@yahoo.com


Solution - Fix & Patch:
The vulnerability can be patched by a secure parse and encode of the vulnerable message body value input.
Filter or encode also the outgoing mails with the vulnerable db stored message body context to prevent script cod executions.

Security Risk:
The security risk of the persistent input validation web vulnerability is estimated as medium(+).

Credits & Authors:
Vulnerability Laboratory [Research Team] - Ateeq ur Rehman Khan (ateeq@evolution-sec.com) [www.vulnerability-lab.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/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@vulnerability-lab.com or research@vulnerability-lab.com) to get a permission.

Copyright © 2014 | Vulnerability Laboratory [Evolution Security]

DOMAIN: www.vulnerability-lab.com
CONTACT: research@vulnerability-lab.com

Login or Register to add favorites

File Archive:

May 2024

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

Top Authors In Last 30 Days

File Tags


packet storm

© 2022 Packet Storm. All rights reserved.

Security Services
Hosting By