exploit the possibilities

Skype Account Service Reset Credentials

Skype Account Service Reset Credentials
Posted Nov 19, 2012
Authored by Benjamin Kunz Mejri, Chokri Ben Achor | Site vulnerability-lab.com

The Skype Account Service application suffered from a reset password/username vulnerability.

tags | exploit
MD5 | 1b8b33483a64506397dd6c9489db51fd

Skype Account Service Reset Credentials

Change Mirror Download
Title:
======
Skype Account Service - Reset (Session) Password/Username Vulnerability


Date:
=====
2012-11-16


References:
===========
http://www.vulnerability-lab.com/get_content.php?id=720

MSRC ID: 13050[bc]

News:
http://news.softpedia.com/news/Skype-0Day-Vulnerability-Allowed-Hackers-to-Change-the-Password-of-Any-Account-Video-307672.shtml
http://www.scmagazine.com.au/News/323271,skype-account-hijack-hole-patched.aspx



VL-ID:
=====
720


Common Vulnerability Scoring System:
====================================
9.5


Introduction:
=============
Skype is a proprietary voice-over-Internet Protocol service and software application originally created in 2003 by Swedish entrepreneur
Niklas Zennström and his Danish partner Janus Friis. It has been owned by Microsoft since 2011. The service allows users to communicate
with peers by voice, video, and instant messaging over the Internet. Phone calls may be placed to recipients on the traditional telephone
networks. Calls to other users within the Skype service are free of charge, while calls to landline telephones and mobile phones are charged
via a debit-based user account system. Skype has also become popular for its additional features, including file transfer, and videoconferencing.
Competitors include SIP and H.323-based services, such as Linphone, as well as the Google Talk service, Mumble and Hall.com.

Skype has 663 million registered users as of September 2011. The network is operated by Microsoft, which has its Skype division headquarters
in Luxembourg. Most of the development team and 44% of the overall employees of the division are situated in Tallinn and Tartu, Estonia.

Unlike most other VoIP services, Skype is a hybrid peer-to-peer and client–server system. It makes use of background processing on computers
running Skype software. Skype`s original proposed name (Sky Peer-to-Peer) reflects this fact. Some network administrators have banned Skype
on corporate, government, home, and education networks, citing reasons such as inappropriate usage of resources, excessive bandwidth usage,
and security concerns.

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


Abstract:
=========
The Vulnerability Laboratory Research Team discovered a critical session vulnerability in Microsofts Skype Account Service Application.


Report-Timeline:
================
2012-10-01: Researcher Notification & Coordination (VL - Benjamin Kunz Mejri)
2012-10-11: Vendor Notification (Skype Security)
2012-10-11: Vendor Notification (MSRC)
2012-10-23: Vendor Response/Feedback (MSRC)
2012-11-12: Vendor Fix/Patch *Hotfix (Skype)
2012-11-16: Public Disclosure (Vulnerability Laboratory)


Status:
========
Published


Affected Products:
==================
Microsoft
Product: Skype Application & Software Account Service 2012 Q3


Exploitation-Technique:
=======================
Remote


Severity:
=========
Critical


Details:
========
A critical Password Reset (session) vulnerability is detected in Microsofts Skype WebServer Auth System Application.
The vulnerability allows remote attackers without privileged application account to exchange and reset any skype account.

The critical application vulnerability is located in the recovery account function of the skype account service application.
In the recovery function is an auth request bound to the account session using the json form with jquery and the value of the intercape.
The request itself is not sanitized. The value only check if exist and if empty but not validate the context again. The attacker can
bypass the token protection via live session tamper to reset any account by exchanging the values local to his own. Exploitation
requires `processing to request` via jquery implement JSon form request. Since yet it is only manually possible to exploit the remote
vulnerability by using a session tamper tools like tamper data. A remote attacker can, for example bypass the token protection with
values like “*/+[New Account Details] or [New Account Details]+/*“ to reset random skype application accounts or infiltrate specific
choosen account by changing usernames or passwords.

Successful exploitation of the critical remote vulnerability result in skype account compromise, skype account infiltration,
mail information disclosure or lead to skype user account manipulation.


Vulnerable Service(s):
[+] Microsoft - Skype Service - https://login.skype.com/

Vulnerable Section(s):
[+] Account Application Service - https://login.skype.com/account

Vulnerable Module(s):
[+] Recovery Function - https://login.skype.com/account/password-automation

Vulnerable Module(s):
[+] JSon & jquery


Proof of Concept:
=================
The vulnerability can be exploited by remote attacker without required user inter action.
For demonstration or reproduce ...

Required for Exploitation:
[+] Tamper Data or other live tamper software
[+] Web Browser like mozilla firefox, ie9 or chrome
[+] A random registered skype user account to get a not expired session

Exploitation Techique(s):
[+] Bypass the Skype Recovery Page (request tamper) to New Pass or Reset
[+] Bypass token protection via not empty value with positiv value(s) to match
[+] Hold the request via tamper include own values to setup the new password

Next Step(s):
[+] Decode captcha & send automatique value(s) -> Account Service (Remote Exploit)

Reference(s):
[+] https://login.skype.com/account/password-automation

Video(PoC Demo):
[+] http://www.youtube.com/watch?v=RPTEaJftNw0


Solution:
=========
2012-11-12: Vendor Fix/Patch (Skype)


Risk:
=====
The security risk of the remote password and username reset (session) vulnerability is estimated as critical.


Credits:
========
Vulnerability Laboratory [Research Team] - Benjamin Kunz Mejri (bkm@vulnerability-lab.com)
Vulnerability Laboratory [Research Team] - Chokri Ben Achour (meister@vulnerability-lab.com)


Disclaimer:
===========
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.vulnerability-lab.com/register
Contact: admin@vulnerability-lab.com - support@vulnerability-lab.com - research@vulnerability-lab.com
Section: video.vulnerability-lab.com - forum.vulnerability-lab.com - news.vulnerability-lab.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

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, sourcecode, 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 support@vulnerability-lab.com) to get a permission.

Copyright © 2012 | Vulnerability Laboratory

--
VULNERABILITY RESEARCH LABORATORY
LABORATORY RESEARCH TEAM
CONTACT: research@vulnerability-lab.com

Comments

RSS Feed Subscribe to this comment feed

No comments yet, be the first!

Login or Register to post a comment

File Archive:

July 2019

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