CVE-2010-3679

UnknownEPSS 12.23%

Last modified

CVE-2010-3679 is a vulnerability of currently unknown severity. Oracle MySQL 5.1 before 5.1.49 allows remote authenticated users to cause a denial of service (mysqld daemon crash) via certain arguments to the BINLOG command, which triggers an access of uninitialized memory, as demonstrated by valgrind.. EPSS estimates a 12.23% chance of exploitation in the next 30 days.

Description

Oracle MySQL 5.1 before 5.1.49 allows remote authenticated users to cause a denial of service (mysqld daemon crash) via certain arguments to the BINLOG command, which triggers an access of uninitialized memory, as demonstrated by valgrind.

Metrics

EPSS Probability
12.23%

95.6th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersionsUpdate
MysqlMysql5.1.5
MysqlMysql5.1.23
MysqlMysql5.1.31
MysqlMysql5.1.32
MysqlMysql5.1.34
MysqlMysql5.1.37
OracleMysql5.1
OracleMysql5.1.1
OracleMysql5.1.2
OracleMysql5.1.3
OracleMysql5.1.4
OracleMysql5.1.6
OracleMysql5.1.7
OracleMysql5.1.8
OracleMysql5.1.9
OracleMysql5.1.10
OracleMysql5.1.11
OracleMysql5.1.12
OracleMysql5.1.13
OracleMysql5.1.14
OracleMysql5.1.15
OracleMysql5.1.16
OracleMysql5.1.17
OracleMysql5.1.18
OracleMysql5.1.19
OracleMysql5.1.20
OracleMysql5.1.21
OracleMysql5.1.22
OracleMysql5.1.23A
OracleMysql5.1.24
OracleMysql5.1.25
OracleMysql5.1.26
OracleMysql5.1.27
OracleMysql5.1.28
OracleMysql5.1.29
OracleMysql5.1.30
OracleMysql5.1.31Sp1
OracleMysql5.1.33
OracleMysql5.1.34Sp1
OracleMysql5.1.35
OracleMysql5.1.36
OracleMysql5.1.37Sp1
OracleMysql5.1.38
OracleMysql5.1.39
OracleMysql5.1.40
OracleMysql5.1.41
OracleMysql5.1.42
OracleMysql5.1.43
OracleMysql5.1.44
OracleMysql5.1.45

Showing 50 of 53 affected configurations. See NVD for the full list.

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2010-3679?
Oracle MySQL 5.1 before 5.1.49 allows remote authenticated users to cause a denial of service (mysqld daemon crash) via certain arguments to the BINLOG command, which triggers an access of uninitialized memory, as demonstrated by valgrind.
How severe is CVE-2010-3679?
Severity scoring for CVE-2010-3679 is pending analysis. The EPSS model estimates a 12.23% probability of exploitation in the next 30 days.
How do I fix CVE-2010-3679?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2010-3679?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST