CVE-2005-0710

Public Exploit

Description

MySQL 4.0.23 and earlier, and 4.1.x up to 4.1.10, allows remote authenticated users with INSERT and DELETE privileges to bypass library path restrictions and execute arbitrary libraries by using INSERT INTO to modify the mysql.func table, which is processed by the udf_init function.

4.6

CVSS

Severity: Medium

CVSS 2.0 •

EPSS 30.54% Top 5%

Vendor Advisory trustix.org Vendor Advisory debian.org Vendor Advisory redhat.com Vendor Advisory sun.com Vendor Advisory novell.com Vendor Advisory ubuntu.com Vendor Advisory redhat.com Vendor Advisory apple.com Vendor Advisory mandriva.com Vendor Advisory gentoo.org Vendor Advisory apple.com

Affected: n/a n/a

References

Link	Tags
http://www.trustix.org/errata/2005/0009/	vendor advisory
http://marc.info/?l=bugtraq&m=111065974004648&w=2	mailing list
http://www.debian.org/security/2005/dsa-707	patch vendor advisory
http://www.redhat.com/support/errata/RHSA-2005-334.html	vendor advisory
http://sunsolve.sun.com/search/document.do?assetkey=1-26-101864-1	vendor advisory
http://www.novell.com/linux/security/advisories/2005_19_mysql.html	patch vendor advisory
https://usn.ubuntu.com/96-1/	vendor advisory
http://www.redhat.com/support/errata/RHSA-2005-348.html	vendor advisory
http://archives.neohapsis.com/archives/vulnwatch/2005-q1/0083.html	mailing list exploit
http://lists.apple.com/archives/security-announce/2005/Aug/msg00000.html	vendor advisory
http://www.mandriva.com/security/advisories?name=MDKSA-2005:060	vendor advisory
https://exchange.xforce.ibmcloud.com/vulnerabilities/19658	vdb entry
http://www.gentoo.org/security/en/glsa/glsa-200503-19.xml	patch vendor advisory
https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A10180	vdb entry signature
http://lists.apple.com/archives/security-announce/2005//Aug/msg00001.html	vendor advisory
http://www.securityfocus.com/bid/12781	vdb entry patch

Frequently Asked Questions

What is the severity of CVE-2005-0710?: CVE-2005-0710 has been scored as a medium severity vulnerability.
How to fix CVE-2005-0710?: To fix CVE-2005-0710, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2005-0710 being actively exploited in the wild?: It is possible that CVE-2005-0710 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~31% probability that this vulnerability will be exploited by malicious actors in the next 30 days.