CVE-2017-1297 : Détail

CVE-2017-1297

7.3
/
Haute
Overflow
0.06%V3
Local
2017-06-27
14h00 +00:00
2017-08-11
13h57 +00:00
Notifications pour un CVE
Restez informé de toutes modifications pour un CVE spécifique.
Gestion des notifications

Descriptions du CVE

IBM DB2 for Linux, UNIX and Windows 9.2, 10.1, 10.5, and 11.1 (includes DB2 Connect Server) is vulnerable to a stack-based buffer overflow, caused by improper bounds checking which could allow a local attacker to execute arbitrary code. IBM X-Force ID: 125159.

Informations du CVE

Faiblesses connexes

CWE-ID Nom de la faiblesse Source
CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data.

Métriques

Métriques Score Gravité CVSS Vecteur Source
V3.0 7.3 HIGH CVSS:3.0/AV:L/AC:L/PR:L/UI:R/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.

Local

A vulnerability exploitable with Local access means that the vulnerable component is not bound to the network stack, and the attacker's path is via read/write/execute capabilities. In some cases, the attacker may be logged in locally in order to exploit the vulnerability, otherwise, she may rely on User Interaction to execute a malicious file.

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.

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.

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 4.4 AV:L/AC:M/Au:N/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.

Informations sur l'Exploit

Exploit Database EDB-ID : 42260

Date de publication : 2017-06-25 22h00 +00:00
Auteur : defensecode
EDB Vérifié : No

''' DefenseCode Security Advisory IBM DB2 Command Line Processor Buffer Overflow Advisory ID: DC-2017-04-002 Advisory Title: IBM DB2 Command Line Processor Buffer Overflow Advisory URL: http://www.defensecode.com/advisories/IBM_DB2_Command_Line_Processor_Buffer_Overflow.pdf Software: IBM DB2 Version: V9.7, V10.1, V10.5 and V11.1 on all platforms Vendor Status: Vendor Contacted / Fixed (CVE-2017-1297) Release Date: 26.06.2017 Risk: High 1. General Overview =================== IBM DB2 for Linux, UNIX and Windows (includes DB2 Connect Server) Command Line Process (CLP) is vulnerable to a stack based buffer overflow, caused by improper bounds checking which could allow an attacker to execute arbitrary code. The vulnerability is triggered by providing an overly long procedure name inside a CALL statement. 2. Software Overview =================== DB2 is a database product from IBM. It is a Relational Database Management System. DB2 is designed to store, analyze and retrieve the data efficiently. DB2 currently supports Linux, UNIX and Windows platforms. db2bp is a persistent background process for the DB2 Command Line Processor, and it is the process which actually connects to the database. 3. Brief Vulnerability Description ================================== By providing a specially crafted command file to the db2 CLP utility, it is possible to cause a buffer overflow and possibly hijack the execution flow of the program. Crafted file contains a CALL statement with an overly long procedure parameter. 3.1 Proof of Concept The following python script will generate a proof of concept .sql crash test file that can be used to verify the vulnerability: ------- ''' #!/usr/bin/python load_overflow = 'A' * 1000 statement = "CALL " + load_overflow + ";" crash_file = open("crash.sql", "w") crash_file.write(statement) crash_file.close() ''' ------- PoC usage: db2 -f crash.sql 4. Credits ========== Vulnerability discovered by Leon Juranic, further analysis by Bosko Stankovic. 5. About DefenseCode ================================ DefenseCode L.L.C. delivers products and services designed to analyze and test web, desktop and mobile applications for security vulnerabilities. DefenseCode ThunderScan is a SAST (Static Application Security Testing, WhiteBox Testing) solution for performing extensive security audits of application source code. ThunderScan performs fast and accurate analyses of large and complex source code projects delivering precise results and low false positive rate. DefenseCode WebScanner is a DAST (Dynamic Application Security Testing, BlackBox Testing) solution for comprehensive security audits of active web applications. WebScanner will test a website's security by carrying out a large number of attacks using the most advanced techniques, just as a real attacker would. Subscribe for free software trial on our website http://www.defensecode.com/ '''

Products Mentioned

Configuraton 0

Ibm>>Data_server_client >> Version -

Ibm>>Data_server_driver_for_odbc_and_cli >> Version -

Ibm>>Data_server_driver_package >> Version -

Ibm>>Data_server_runtime_client >> Version -

Ibm>>Db2 >> Version 9.7

Ibm>>Db2 >> Version 9.7

Ibm>>Db2 >> Version 9.7

Ibm>>Db2 >> Version 9.7

Ibm>>Db2 >> Version 9.7

Ibm>>Db2 >> Version 10.1

Ibm>>Db2 >> Version 10.1

Ibm>>Db2 >> Version 10.1

Ibm>>Db2 >> Version 10.1

Ibm>>Db2 >> Version 10.1

Ibm>>Db2 >> Version 10.5

Ibm>>Db2 >> Version 10.5

Ibm>>Db2 >> Version 10.5

Ibm>>Db2 >> Version 10.5

Ibm>>Db2 >> Version 10.5

Ibm>>Db2 >> Version 11.1

Ibm>>Db2 >> Version 11.1

Ibm>>Db2 >> Version 11.1

Ibm>>Db2 >> Version 11.1

Ibm>>Db2 >> Version 11.1

Ibm>>Db2_connect >> Version 9.7

Ibm>>Db2_connect >> Version 9.7

Ibm>>Db2_connect >> Version 9.7

Ibm>>Db2_connect >> Version 10.1

Ibm>>Db2_connect >> Version 10.1

Ibm>>Db2_connect >> Version 10.1

Ibm>>Db2_connect >> Version 10.5

Ibm>>Db2_connect >> Version 10.5

Ibm>>Db2_connect >> Version 10.5

Ibm>>Db2_connect >> Version 11.1.0.0

Ibm>>Db2_connect >> Version 11.1.0.0

Ibm>>Db2_connect >> Version 11.1.0.0

Linux>>Linux_kernel >> Version -

Microsoft>>Windows >> Version -

Références

http://www.securityfocus.com/bid/99271
Tags : vdb-entry, x_refsource_BID
http://www.securitytracker.com/id/1038772
Tags : vdb-entry, x_refsource_SECTRACK
https://www.exploit-db.com/exploits/42260/
Tags : exploit, x_refsource_EXPLOIT-DB