Vulnerabilities > CVE-2017-8438 - Improper Privilege Management vulnerability in Elastic X-Pack
Attack vector
NETWORK Attack complexity
LOW Privileges required
LOW Confidentiality impact
HIGH Integrity impact
HIGH Availability impact
HIGH Summary
Elastic X-Pack Security versions 5.0.0 to 5.4.0 contain a privilege escalation bug in the run_as functionality. This bug prevents transitioning into the specified user specified in a run_as request. If a role has been created using a template that contains the _user properties, the behavior of run_as will be incorrect. Additionally if the run_as user specified does not exist, the transition will not happen.
Vulnerable Configurations
Part | Description | Count |
---|---|---|
Application | 13 |
Common Weakness Enumeration (CWE)
Common Attack Pattern Enumeration and Classification (CAPEC)
- Restful Privilege Elevation Rest uses standard HTTP (Get, Put, Delete) style permissions methods, but these are not necessarily correlated generally with back end programs. Strict interpretation of HTTP get methods means that these HTTP Get services should not be used to delete information on the server, but there is no access control mechanism to back up this logic. This means that unless the services are properly ACL'd and the application's service implementation are following these guidelines then an HTTP request can easily execute a delete or update on the server side. The attacker identifies a HTTP Get URL such as http://victimsite/updateOrder, which calls out to a program to update orders on a database or other resource. The URL is not idempotent so the request can be submitted multiple times by the attacker, additionally, the attacker may be able to exploit the URL published as a Get method that actually performs updates (instead of merely retrieving data). This may result in malicious or inadvertent altering of data on the server.
Nessus
NASL family | CGI abuses |
NASL id | ELASTICSEARCH_ESA_2017_06.NASL |
description | X-Pack Security versions 5.0.0 to 5.4.0 contain a privilege escalation bug in the run_as functionality. This bug prevents transitioning into the specified user specified in a run_as request. If a role has been created using a template that contains the _user properties, the behavior of run_as will be incorrect. Additionally if the run_as user specified does not exist, the transition will not happen. |
last seen | 2020-06-01 |
modified | 2020-06-02 |
plugin id | 112038 |
published | 2018-08-22 |
reporter | This script is Copyright (C) 2018-2019 and is owned by Tenable, Inc. or an Affiliate thereof. |
source | https://www.tenable.com/plugins/nessus/112038 |
title | Elasticsearch ESA-2017-06 |
code |
|
References
- https://discuss.elastic.co/t/elastic-stack-5-4-1-and-5-3-3-security-updates/87952
- https://discuss.elastic.co/t/elastic-stack-5-4-1-and-5-3-3-security-updates/87952
- https://www.elastic.co/blog/elasticsearch-5-4-1-and-5-3-3-released
- https://www.elastic.co/blog/elasticsearch-5-4-1-and-5-3-3-released
- https://www.elastic.co/community/security
- https://www.elastic.co/community/security