ID CVE-2013-0084
Summary Directory traversal vulnerability in Microsoft SharePoint Server 2010 SP1 and SharePoint Foundation 2010 SP1 allows remote attackers to bypass intended read restrictions for content, and hijack user accounts, via a crafted URL, aka "SharePoint Directory Traversal Vulnerability."
References
Vulnerable Configurations
  • cpe:2.3:a:microsoft:sharepoint_foundation:2010:sp1:*:*:*:*:*:*
    cpe:2.3:a:microsoft:sharepoint_foundation:2010:sp1:*:*:*:*:*:*
  • cpe:2.3:a:microsoft:sharepoint_server:2010:sp1:*:*:*:*:*:*
    cpe:2.3:a:microsoft:sharepoint_server:2010:sp1:*:*:*:*:*:*
CVSS
Base: 7.5 (as of 12-10-2018 - 22:03)
Impact:
Exploitability:
CWE CWE-22
CAPEC
  • Manipulating Web Input to File System Calls
    An attacker manipulates inputs to the target software which the target software passes to file system calls in the OS. The goal is to gain access to, and perhaps modify, areas of the file system that the target software did not intend to be accessible.
  • Using Slashes and URL Encoding Combined to Bypass Validation Logic
    This attack targets the encoding of the URL combined with the encoding of the slash characters. An attacker can take advantage of the multiple ways of encoding a URL and abuse the interpretation of the URL. A URL may contain special character that need special syntax handling in order to be interpreted. Special characters are represented using a percentage character followed by two digits representing the octet code of the original character (%HEX-CODE). For instance US-ASCII space character would be represented with %20. This is often referred as escaped ending or percent-encoding. Since the server decodes the URL from the requests, it may restrict the access to some URL paths by validating and filtering out the URL requests it received. An attacker will try to craft an URL with a sequence of special characters which once interpreted by the server will be equivalent to a forbidden URL. It can be difficult to protect against this attack since the URL can contain other format of encoding such as UTF-8 encoding, Unicode-encoding, etc.
  • Using Escaped Slashes in Alternate Encoding
    This attack targets the use of the backslash in alternate encoding. An attacker can provide a backslash as a leading character and causes a parser to believe that the next character is special. This is called an escape. By using that trick, the attacker tries to exploit alternate ways to encode the same character which leads to filter problems and opens avenues to attack.
  • Path Traversal
    An adversary uses path manipulation methods to exploit insufficient input validation of a target to obtain access to data that should be not be retrievable by ordinary well-formed requests. A typical variety of this attack involves specifying a path to a desired file together with dot-dot-slash characters, resulting in the file access API or function traversing out of the intended directory structure and into the root file system. By replacing or modifying the expected path information the access function or API retrieves the file desired by the attacker. These attacks either involve the attacker providing a complete path to a targeted file or using control characters (e.g. path separators (/ or \) and/or dots (.)) to reach desired directories or files.
  • Using Slashes in Alternate Encoding
    This attack targets the encoding of the Slash characters. An attacker would try to exploit common filtering problems related to the use of the slashes characters to gain access to resources on the target host. Directory-driven systems, such as file systems and databases, typically use the slash character to indicate traversal between directories or other container components. For murky historical reasons, PCs (and, as a result, Microsoft OSs) choose to use a backslash, whereas the UNIX world typically makes use of the forward slash. The schizophrenic result is that many MS-based systems are required to understand both forms of the slash. This gives the attacker many opportunities to discover and abuse a number of common filtering problems. The goal of this pattern is to discover server software that only applies filters to one version, but not the other.
Access
VectorComplexityAuthentication
NETWORK LOW NONE
Impact
ConfidentialityIntegrityAvailability
PARTIAL PARTIAL PARTIAL
cvss-vector via4 AV:N/AC:L/Au:N/C:P/I:P/A:P
msbulletin via4
bulletin_id MS13-024
bulletin_url
date 2013-03-12T00:00:00
impact Elevation of Privilege
knowledgebase_id 2780176
knowledgebase_url
severity Critical
title Vulnerabilities in SharePoint Could Allow Elevation of Privilege
oval via4
accepted 2014-12-08T04:00:12.814-05:00
class vulnerability
contributors
  • name SecPod Team
    organization SecPod Technologies
  • name Kumarswamy S
    organization SecPod Technologies
definition_extensions
comment Microsoft SharePoint Foundation 2010 Service Pack 1 is installed
oval oval:org.mitre.oval:def:15661
description Directory traversal vulnerability in Microsoft SharePoint Server 2010 SP1 and SharePoint Foundation 2010 SP1 allows remote attackers to bypass intended read restrictions for content, and hijack user accounts, via a crafted URL, aka "SharePoint Directory Traversal Vulnerability."
family windows
id oval:org.mitre.oval:def:16445
status accepted
submitted 2013-03-14T12:59:10
title SharePoint Directory Traversal Vulnerability - MS13-024
version 10
refmap via4
cert TA13-071A
Last major update 12-10-2018 - 22:03
Published 13-03-2013 - 00:55
Last modified 12-10-2018 - 22:03
Back to Top