CVE-2009-5026 : Detail

CVE-2009-5026

SQL Injection
A03-Injection
1.08%V3
Network
2012-08-16
22h00 +00:00
2012-10-13
07h00 +00:00
CVE.org
NVD
Notifications for a CVE
Stay informed of any changes for a specific CVE.
Notifications manage

CVE Descriptions

The executable comment feature in MySQL 5.0.x before 5.0.93 and 5.1.x before 5.1.50, when running in certain slave configurations in which the slave is running a newer version than the master, allows remote attackers to execute arbitrary SQL commands via custom comments.

CVE Informations

Related Weaknesses

CWE-ID Weakness Name Source
CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.

Metrics

Metrics Score Severity CVSS Vector Source
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

Exploit information

Exploit Database EDB-ID : 34796

Publication date : 2010-08-02
22h00 +00:00
Author : Libing Song
EDB Verified : Yes

source: https://www.securityfocus.com/bid/43677/info MySQL is prone to a remote privilege-escalation vulnerability. An attacker can exploit this issue to run arbitrary SQL statements with 'SUPER' privileges on the slave database system. This will allow the attacker to compromise the affected database system. This issue affects versions prior to MySQL 5.1.50. UPDATE db1.tbl1 /*!514900 ,mysql.user */ SET db1.tbl1.col1=2 /*!514900 ,mysql.user.Super_priv='Y' WHERE mysql.user.User='user1'*/;

Products Mentioned

Configuraton 0

Mysql>>Mysql >> Version 5.0.0

Mysql>>Mysql >> Version 5.0.1

Mysql>>Mysql >> Version 5.0.2

Mysql>>Mysql >> Version 5.0.3

Mysql>>Mysql >> Version 5.0.4

Mysql>>Mysql >> Version 5.0.5

Mysql>>Mysql >> Version 5.0.10

Mysql>>Mysql >> Version 5.0.15

Mysql>>Mysql >> Version 5.0.16

Mysql>>Mysql >> Version 5.0.17

Mysql>>Mysql >> Version 5.0.20

Mysql>>Mysql >> Version 5.0.24

Mysql>>Mysql >> Version 5.0.45

    Mysql>>Mysql >> Version 5.0.82

    Mysql>>Mysql >> Version 5.0.84

    Mysql>>Mysql >> Version 5.0.87

    Oracle>>Mysql >> Version 5.0.23

    Oracle>>Mysql >> Version 5.0.41

    Oracle>>Mysql >> Version 5.0.45

    Oracle>>Mysql >> Version 5.0.51

    Oracle>>Mysql >> Version 5.0.67

    Oracle>>Mysql >> Version 5.0.75

    Oracle>>Mysql >> Version 5.0.77

    Oracle>>Mysql >> Version 5.0.81

    Oracle>>Mysql >> Version 5.0.83

    Oracle>>Mysql >> Version 5.0.85

    Oracle>>Mysql >> Version 5.0.86

    Oracle>>Mysql >> Version 5.0.88

    Oracle>>Mysql >> Version 5.0.89

    Oracle>>Mysql >> Version 5.0.90

    Oracle>>Mysql >> Version 5.0.91

    Oracle>>Mysql >> Version 5.0.92

    Configuraton 0

    Mysql>>Mysql >> Version 5.1.23

    Mysql>>Mysql >> Version 5.1.31

    Mysql>>Mysql >> Version 5.1.32

    Mysql>>Mysql >> Version 5.1.34

    Mysql>>Mysql >> Version 5.1.37

    Oracle>>Mysql >> Version 5.1

    Oracle>>Mysql >> Version 5.1.1

    Oracle>>Mysql >> Version 5.1.2

    Oracle>>Mysql >> Version 5.1.3

    Oracle>>Mysql >> Version 5.1.4

    Oracle>>Mysql >> Version 5.1.10

    Oracle>>Mysql >> Version 5.1.11

    Oracle>>Mysql >> Version 5.1.12

    Oracle>>Mysql >> Version 5.1.13

    Oracle>>Mysql >> Version 5.1.14

    Oracle>>Mysql >> Version 5.1.15

    Oracle>>Mysql >> Version 5.1.16

    Oracle>>Mysql >> Version 5.1.17

    Oracle>>Mysql >> Version 5.1.18

    Oracle>>Mysql >> Version 5.1.19

    Oracle>>Mysql >> Version 5.1.20

    Oracle>>Mysql >> Version 5.1.21

    Oracle>>Mysql >> Version 5.1.22

    Oracle>>Mysql >> Version 5.1.23

    Oracle>>Mysql >> Version 5.1.24

    Oracle>>Mysql >> Version 5.1.25

    Oracle>>Mysql >> Version 5.1.26

    Oracle>>Mysql >> Version 5.1.27

    Oracle>>Mysql >> Version 5.1.28

    Oracle>>Mysql >> Version 5.1.29

    Oracle>>Mysql >> Version 5.1.30

    Oracle>>Mysql >> Version 5.1.31

    Oracle>>Mysql >> Version 5.1.33

    Oracle>>Mysql >> Version 5.1.34

    Oracle>>Mysql >> Version 5.1.35

    Oracle>>Mysql >> Version 5.1.36

    Oracle>>Mysql >> Version 5.1.37

    Oracle>>Mysql >> Version 5.1.38

    Oracle>>Mysql >> Version 5.1.39

    Oracle>>Mysql >> Version 5.1.40

    Oracle>>Mysql >> Version 5.1.40

    Oracle>>Mysql >> Version 5.1.41

    Oracle>>Mysql >> Version 5.1.42

    Oracle>>Mysql >> Version 5.1.43

    Oracle>>Mysql >> Version 5.1.43

    Oracle>>Mysql >> Version 5.1.44

    Oracle>>Mysql >> Version 5.1.45

    Oracle>>Mysql >> Version 5.1.46

    Oracle>>Mysql >> Version 5.1.46

    Oracle>>Mysql >> Version 5.1.47

    Oracle>>Mysql >> Version 5.1.48

    Oracle>>Mysql >> Version 5.1.49

    Oracle>>Mysql >> Version 5.1.49

    References

    http://bugs.mysql.com/bug.php?id=49124
    Tags : x_refsource_CONFIRM
    http://seclists.org/oss-sec/2011/q4/101
    Tags : mailing-list, x_refsource_MLIST
    http://secunia.com/advisories/49179
    Tags : third-party-advisory, x_refsource_SECUNIA