ID CVE-2018-7431
Summary Directory traversal vulnerability in the Splunk Django App in Splunk Enterprise 6.0.x before 6.0.14, 6.1.x before 6.1.13, 6.2.x before 6.2.14, 6.3.x before 6.3.10, 6.4.x before 6.4.6, and 6.5.x before 6.5.3; and Splunk Light before 6.6.0 allows remote authenticated users to read arbitrary files via unspecified vectors.
References
Vulnerable Configurations
  • Splunk 6.0.0 Enterprise
    cpe:2.3:a:splunk:splunk:6.0.0:-:-:-:enterprise
  • Splunk 6.0.1 Enterprise
    cpe:2.3:a:splunk:splunk:6.0.1:-:-:-:enterprise
  • Splunk 6.0.2 Enterprise
    cpe:2.3:a:splunk:splunk:6.0.2:-:-:-:enterprise
  • Splunk 6.0.3 Enterprise
    cpe:2.3:a:splunk:splunk:6.0.3:-:-:-:enterprise
  • Splunk 6.0.4 Enterprise
    cpe:2.3:a:splunk:splunk:6.0.4:-:-:-:enterprise
  • Splunk 6.0.5 Enterprise
    cpe:2.3:a:splunk:splunk:6.0.5:-:-:-:enterprise
  • Splunk 6.0.6 Enterprise
    cpe:2.3:a:splunk:splunk:6.0.6:-:-:-:enterprise
  • Splunk 6.0.7 Enterprise
    cpe:2.3:a:splunk:splunk:6.0.7:-:-:-:enterprise
  • Splunk 6.0.8 Enterprise
    cpe:2.3:a:splunk:splunk:6.0.8:-:-:-:enterprise
  • Splunk 6.0.9 Enterprise
    cpe:2.3:a:splunk:splunk:6.0.9:-:-:-:enterprise
  • Splunk 6.0.10 Enterprise
    cpe:2.3:a:splunk:splunk:6.0.10:-:-:-:enterprise
  • Splunk 6.0.11 Enterprise
    cpe:2.3:a:splunk:splunk:6.0.11:-:-:-:enterprise
  • Splunk 6.0.12 Enterprise
    cpe:2.3:a:splunk:splunk:6.0.12:-:-:-:enterprise
  • Splunk 6.1.0 Enterprise
    cpe:2.3:a:splunk:splunk:6.1.0:-:-:-:enterprise
  • Splunk Enterprise 6.1.3
    cpe:2.3:a:splunk:splunk:6.1.3:-:-:-:enterprise
  • Splunk 6.1.4 Enterprise
    cpe:2.3:a:splunk:splunk:6.1.4:-:-:-:enterprise
  • Splunk 6.1.5 Enterprise
    cpe:2.3:a:splunk:splunk:6.1.5:-:-:-:enterprise
  • Splunk 6.1.6 Enterprise
    cpe:2.3:a:splunk:splunk:6.1.6:-:-:-:enterprise
  • Splunk 6.1.7 Enterprise
    cpe:2.3:a:splunk:splunk:6.1.7:-:-:-:enterprise
  • Splunk 6.1.8 Enterprise
    cpe:2.3:a:splunk:splunk:6.1.8:-:-:-:enterprise
  • Splunk 6.1.9 Enterprise
    cpe:2.3:a:splunk:splunk:6.1.9:-:-:-:enterprise
  • Splunk 6.1.10 Enterprise
    cpe:2.3:a:splunk:splunk:6.1.10:-:-:-:enterprise
  • Splunk 6.1.11 Enterprise
    cpe:2.3:a:splunk:splunk:6.1.11:-:-:-:enterprise
  • Splunk 6.2.0 Enterprise
    cpe:2.3:a:splunk:splunk:6.2.0:-:-:-:enterprise
  • Splunk 6.2.0 Light
    cpe:2.3:a:splunk:splunk:6.2.0:-:-:-:light
  • Splunk 6.2.1 Enterprise
    cpe:2.3:a:splunk:splunk:6.2.1:-:-:-:enterprise
  • Splunk 6.2.1 Light
    cpe:2.3:a:splunk:splunk:6.2.1:-:-:-:light
  • Splunk 6.2.2 Enterprise
    cpe:2.3:a:splunk:splunk:6.2.2:-:-:-:enterprise
  • Splunk 6.2.2 Light
    cpe:2.3:a:splunk:splunk:6.2.2:-:-:-:light
  • Splunk 6.2.3 Enterprise
    cpe:2.3:a:splunk:splunk:6.2.3:-:-:-:enterprise
  • Splunk 6.2.3 Light
    cpe:2.3:a:splunk:splunk:6.2.3:-:-:-:light
  • Splunk 6.2.6 Enterprise
    cpe:2.3:a:splunk:splunk:6.2.6:-:-:-:enterprise
  • Splunk 6.2.7 Enterprise
    cpe:2.3:a:splunk:splunk:6.2.7:-:-:-:enterprise
  • Splunk 6.2.8 Enterprise
    cpe:2.3:a:splunk:splunk:6.2.8:-:-:-:enterprise
  • Splunk 6.2.9 Enterprise
    cpe:2.3:a:splunk:splunk:6.2.9:-:-:-:enterprise
  • Splunk 6.2.10 Enterprise
    cpe:2.3:a:splunk:splunk:6.2.10:-:-:-:enterprise
  • Splunk 6.2.11 Enterprise
    cpe:2.3:a:splunk:splunk:6.2.11:-:-:-:enterprise
  • Splunk 6.2.12 Enterprise
    cpe:2.3:a:splunk:splunk:6.2.12:-:-:-:enterprise
  • Splunk 6.3.0 Enterprise
    cpe:2.3:a:splunk:splunk:6.3.0:-:-:-:enterprise
  • Splunk 6.3.0 Light
    cpe:2.3:a:splunk:splunk:6.3.0:-:-:-:light
  • Splunk 6.3.1 Enterprise
    cpe:2.3:a:splunk:splunk:6.3.1:-:-:-:enterprise
  • Splunk 6.3.1 Light
    cpe:2.3:a:splunk:splunk:6.3.1:-:-:-:light
  • Splunk 6.3.2 Enterprise
    cpe:2.3:a:splunk:splunk:6.3.2:-:-:-:enterprise
  • Splunk 6.3.2 Light
    cpe:2.3:a:splunk:splunk:6.3.2:-:-:-:light
  • Splunk 6.3.3 Enterprise
    cpe:2.3:a:splunk:splunk:6.3.3:-:-:-:enterprise
  • Splunk 6.3.3 Light
    cpe:2.3:a:splunk:splunk:6.3.3:-:-:-:light
  • Splunk 6.3.4 Enterprise
    cpe:2.3:a:splunk:splunk:6.3.4:-:-:-:enterprise
  • Splunk 6.3.4 Light
    cpe:2.3:a:splunk:splunk:6.3.4:-:-:-:light
  • Splunk 6.3.5 Enterprise
    cpe:2.3:a:splunk:splunk:6.3.5:-:-:-:enterprise
  • Splunk 6.3.6 Enterprise
    cpe:2.3:a:splunk:splunk:6.3.6:-:-:-:enterprise
  • Splunk 6.3.7 Enterprise
    cpe:2.3:a:splunk:splunk:6.3.7:-:-:-:enterprise
  • Splunk 6.3.8 Enterprise
    cpe:2.3:a:splunk:splunk:6.3.8:-:-:-:enterprise
  • Splunk 6.4.0 Enterprise
    cpe:2.3:a:splunk:splunk:6.4.0:-:-:-:enterprise
  • Splunk 6.4.1 Enterprise
    cpe:2.3:a:splunk:splunk:6.4.1:-:-:-:enterprise
  • Splunk 6.4.2 Enterprise
    cpe:2.3:a:splunk:splunk:6.4.2:-:-:-:enterprise
  • Splunk 6.4.2 Light
    cpe:2.3:a:splunk:splunk:6.4.2:-:-:-:light
  • Splunk 6.4.3 Enterprise
    cpe:2.3:a:splunk:splunk:6.4.3:-:-:-:enterprise
  • Splunk 6.4.4 Enterprise
    cpe:2.3:a:splunk:splunk:6.4.4:-:-:-:enterprise
  • Splunk 6.5.0 Enterprise
    cpe:2.3:a:splunk:splunk:6.5.0:-:-:-:enterprise
  • Splunk 6.5.1 Enterprise
    cpe:2.3:a:splunk:splunk:6.5.1:-:-:-:enterprise
  • Splunk 6.5.1 Light
    cpe:2.3:a:splunk:splunk:6.5.1:-:-:-:light
CVSS
Base: 4.0
Impact:
Exploitability:
CWE CWE-22
CAPEC
  • Relative Path Traversal
    An attacker exploits a weakness in input validation on the target by supplying a specially constructed path utilizing dot and slash characters for the purpose of obtaining access to arbitrary files or resources. An attacker modifies a known path on the target in order to reach material that is not available through intended channels. These attacks normally involve adding additional path separators (/ or \) and/or dots (.), or encodings thereof, in various combinations in order to reach parent directories or entirely separate trees of the target's directory structure.
  • Directory Traversal
    An attacker with access to file system resources, either directly or via application logic, will use various file path specification or navigation mechanisms such as ".." in path strings and absolute paths to extend their range of access to inappropriate areas of the file system. The attacker attempts to either explore the file system for recon purposes or access directories and files that are intended to be restricted from their access. Exploring the file system can be achieved through constructing paths presented to directory listing programs, such as "ls" and 'dir', or through specially crafted programs that attempt to explore the file system. The attacker engaging in this type of activity is searching for information that can be used later in a more exploitive attack. Access to restricted directories or files can be achieved through modification of path references utilized by system applications.
  • File System Function Injection, Content Based
    An attack of this type exploits the host's trust in executing remote content including binary files. The files are poisoned with a malicious payload (targeting the file systems accessible by the target software) by the attacker and may be passed through standard channels such as via email, and standard web content like PDF and multimedia files. The attacker exploits known vulnerabilities or handling routines in the target processes. Vulnerabilities of this type have been found in a wide variety of commercial applications from Microsoft Office to Adobe Acrobat and Apple Safari web browser. When the attacker knows the standard handling routines and can identify vulnerabilities and entry points they can be exploited by otherwise seemingly normal content. Once the attack is executed, the attackers' program can access relative directories such as C:\Program Files or other standard system directories to launch further attacks. In a worst case scenario, these programs are combined with other propagation logic and work as a virus.
  • 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 way of encoding an URL and abuse the interpretation of the URL. An 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.
  • Manipulating 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 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.
  • 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.
nessus via4
NASL family CGI abuses
NASL id SPLUNK_MULTI_653.NASL
description According to its self-reported version number, the version of Splunk running on the remote web server is Splunk Light prior to 6.6.0 or Splunk Enterprise 6.0.x prior to 6.0.14, 6.1.x prior to 6.1.13, 6.2.x prior to 6.2.14, 6.3.x prior to 6.3.11, 6.4.x prior to 6.4.8, or 6.5.x prior to 6.5.3. It is, therefore,affected by multiple vulnerabilities: - A cross-site scripting (XSS) vulnerability exists due to improper validation of user-supplied input before returning it to users. An unauthenticated, remote attacker can exploit this, by convincing a user to click a specially crafted URL, to execute arbitrary script code in a user's browser session. (CVE-2018-7427) - A denial of service (DoS) vulnerability exists in the Splunk daemon due to improper validation of HTTP requests. An unauthenticated, remote attacker can exploit this, via a specially crafted HTTP request, to cause the application to stop responding. (CVE-2018-7432) - A directory traversal vulnerability exists in Splunk Django App due to improper validation of user-supplied input by the affected software. An authenticated, remote attacker can exploit this, by sending a URI that contains directory traversal characters, to disclose the contents of files located outside of the server's restricted path. (CVE-2018-7431) - A denial of service (DoS) vulnerability exists in the Splunk daemon due to improper handling of malformed HTTP requests. An unauthenticated, remote attacker can exploit this, via a specially crafted HTTP request, to cause the application to stop responding. (CVE-2018-7429)
last seen 2019-02-21
modified 2019-01-09
plugin id 121043
published 2019-01-09
reporter Tenable
source https://www.tenable.com/plugins/index.php?view=single&id=121043
title Splunk Enterprise 6.0.x < 6.0.14 / 6.1.x < 6.1.13 / 6.2.x < 6.2.14 / 6.3.x < 6.3.11 / 6.4.x < 6.4.8 / 6.5.x < 6.5.3 or Splunk Light < 6.6.0 Multiple Vulnerabilities
refmap via4
confirm https://www.splunk.com/view/SP-CAAAP5T
Last major update 23-10-2018 - 17:31
Published 23-10-2018 - 17:31
Last modified 25-01-2019 - 10:10
Back to Top