CVE-2016-1251 : Detail

CVE-2016-1251

8.1
/
High
Memory Corruption
0.6%V3
Network
2016-11-29
19h00 +00:00
2017-06-30
14h57 +00:00
CVE.org
NVD
Notifications for a CVE
Stay informed of any changes for a specific CVE.
Notifications manage

CVE Descriptions

There is a vulnerability of type use-after-free affecting DBD::mysql (aka DBD-mysql or the Database Interface (DBI) MySQL driver for Perl) 3.x and 4.x before 4.041 when used with mysql_server_prepare=1.

CVE Informations

Related Weaknesses

CWE-ID Weakness Name Source
CWE-416 Use After Free
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.

Metrics

Metrics Score Severity CVSS Vector Source
V3.0 8.1 HIGH CVSS:3.0/AV:N/AC:H/PR:N/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.

High

A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected.

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.

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

EPSS

EPSS is a scoring model that predicts the likelihood of a vulnerability being exploited.

EPSS Score

The EPSS model produces a probability score between 0 and 1 (0 and 100%). The higher the score, the greater the probability that a vulnerability will be exploited.

EPSS Percentile

The percentile is used to rank CVE according to their EPSS score. For example, a CVE in the 95th percentile according to its EPSS score is more likely to be exploited than 95% of other CVE. Thus, the percentile is used to compare the EPSS score of a CVE with that of other CVE.
EPSS First.org

Products Mentioned

Configuraton 0

Dbd-mysql_project>>Dbd-mysql >> Version 3.0000_0

Dbd-mysql_project>>Dbd-mysql >> Version 3.0001_1

Dbd-mysql_project>>Dbd-mysql >> Version 3.0001_2

Dbd-mysql_project>>Dbd-mysql >> Version 3.0001_3

Dbd-mysql_project>>Dbd-mysql >> Version 3.0002_1

Dbd-mysql_project>>Dbd-mysql >> Version 3.0002_2

Dbd-mysql_project>>Dbd-mysql >> Version 3.0002_3

Dbd-mysql_project>>Dbd-mysql >> Version 3.0002_4

Dbd-mysql_project>>Dbd-mysql >> Version 3.0002_5

Dbd-mysql_project>>Dbd-mysql >> Version 3.0003_1

Dbd-mysql_project>>Dbd-mysql >> Version 3.0004_1

Dbd-mysql_project>>Dbd-mysql >> Version 3.0005

Dbd-mysql_project>>Dbd-mysql >> Version 3.0005_1

Dbd-mysql_project>>Dbd-mysql >> Version 3.0007_2

Dbd-mysql_project>>Dbd-mysql >> Version 3.0008_1

Dbd-mysql_project>>Dbd-mysql >> Version 3.0009_1

Dbd-mysql_project>>Dbd-mysql >> Version 4.00

Dbd-mysql_project>>Dbd-mysql >> Version 4.001

Dbd-mysql_project>>Dbd-mysql >> Version 4.002

Dbd-mysql_project>>Dbd-mysql >> Version 4.003

Dbd-mysql_project>>Dbd-mysql >> Version 4.004

Dbd-mysql_project>>Dbd-mysql >> Version 4.005

Dbd-mysql_project>>Dbd-mysql >> Version 4.006

Dbd-mysql_project>>Dbd-mysql >> Version 4.007

Dbd-mysql_project>>Dbd-mysql >> Version 4.008

Dbd-mysql_project>>Dbd-mysql >> Version 4.009

Dbd-mysql_project>>Dbd-mysql >> Version 4.010

Dbd-mysql_project>>Dbd-mysql >> Version 4.011

Dbd-mysql_project>>Dbd-mysql >> Version 4.012

Dbd-mysql_project>>Dbd-mysql >> Version 4.013

Dbd-mysql_project>>Dbd-mysql >> Version 4.014

Dbd-mysql_project>>Dbd-mysql >> Version 4.015

Dbd-mysql_project>>Dbd-mysql >> Version 4.016

Dbd-mysql_project>>Dbd-mysql >> Version 4.017

Dbd-mysql_project>>Dbd-mysql >> Version 4.018

Dbd-mysql_project>>Dbd-mysql >> Version 4.019

Dbd-mysql_project>>Dbd-mysql >> Version 4.020

Dbd-mysql_project>>Dbd-mysql >> Version 4.021

Dbd-mysql_project>>Dbd-mysql >> Version 4.022

Dbd-mysql_project>>Dbd-mysql >> Version 4.023

Dbd-mysql_project>>Dbd-mysql >> Version 4.024

Dbd-mysql_project>>Dbd-mysql >> Version 4.025

Dbd-mysql_project>>Dbd-mysql >> Version 4.026

Dbd-mysql_project>>Dbd-mysql >> Version 4.027

Dbd-mysql_project>>Dbd-mysql >> Version 4.028

Dbd-mysql_project>>Dbd-mysql >> Version 4.029

Dbd-mysql_project>>Dbd-mysql >> Version 4.030_01

Dbd-mysql_project>>Dbd-mysql >> Version 4.030_02

Dbd-mysql_project>>Dbd-mysql >> Version 4.031

Dbd-mysql_project>>Dbd-mysql >> Version 4.032

Dbd-mysql_project>>Dbd-mysql >> Version 4.032_01

Dbd-mysql_project>>Dbd-mysql >> Version 4.032_02

Dbd-mysql_project>>Dbd-mysql >> Version 4.032_03

Dbd-mysql_project>>Dbd-mysql >> Version 4.033

Dbd-mysql_project>>Dbd-mysql >> Version 4.033_01

Dbd-mysql_project>>Dbd-mysql >> Version 4.033_02

Dbd-mysql_project>>Dbd-mysql >> Version 4.033_03

Dbd-mysql_project>>Dbd-mysql >> Version 4.034

Dbd-mysql_project>>Dbd-mysql >> Version 4.035

Dbd-mysql_project>>Dbd-mysql >> Version 4.035_01

Dbd-mysql_project>>Dbd-mysql >> Version 4.035_02

Dbd-mysql_project>>Dbd-mysql >> Version 4.035_03

Dbd-mysql_project>>Dbd-mysql >> Version 4.036

Dbd-mysql_project>>Dbd-mysql >> Version 4.037

Dbd-mysql_project>>Dbd-mysql >> Version 4.037_01

Dbd-mysql_project>>Dbd-mysql >> Version 4.038

Dbd-mysql_project>>Dbd-mysql >> Version 4.038_01

Dbd-mysql_project>>Dbd-mysql >> Version 4.039

Dbd-mysql_project>>Dbd-mysql >> Version 4.040

References

https://tracker.debian.org/news/819888
Tags : x_refsource_CONFIRM
http://www.securityfocus.com/bid/94573
Tags : vdb-entry, x_refsource_BID
https://security.gentoo.org/glsa/201701-51
Tags : vendor-advisory, x_refsource_GENTOO