CVE-2002-1374

Public Exploit

Description

The COM_CHANGE_USER command in MySQL 3.x before 3.23.54, and 4.x before 4.0.6, allows remote attackers to gain privileges via a brute force attack using a one-character password, which causes MySQL to only compare the provided password against the first character of the real password.

7.5

CVSS

Severity: High

CVSS 2.0 •

EPSS 25.36% Top 5%

Vendor Advisory com.br Vendor Advisory linuxsecurity.com Vendor Advisory debian.org Vendor Advisory redhat.com Vendor Advisory mandrakesoft.com Vendor Advisory redhat.com Vendor Advisory marc.info Vendor Advisory novell.com Vendor Advisory redhat.com Vendor Advisory trustix.net Vendor Advisory securityfocus.com Vendor Advisory securityfocus.com

Affected: n/a n/a

References

Link	Tags
http://marc.info/?l=bugtraq&m=103971644013961&w=2	mailing list
http://marc.info/?l=bugtraq&m=104005886114500&w=2	mailing list
http://distro.conectiva.com.br/atualizacoes/?id=a&anuncio=000555	vendor advisory
http://www.linuxsecurity.com/advisories/engarde_advisory-2660.html	patch vendor advisory
http://security.e-matters.de/advisories/042002.html
http://www.debian.org/security/2002/dsa-212	vendor advisory
http://www.redhat.com/support/errata/RHSA-2002-288.html	vendor advisory
http://www.mandrakesoft.com/security/advisories?name=MDKSA-2002:087	vendor advisory
http://www.redhat.com/support/errata/RHSA-2003-166.html	vendor advisory
https://exchange.xforce.ibmcloud.com/vulnerabilities/10847	vdb entry
http://marc.info/?l=bugtraq&m=104004857201968&w=2	vendor advisory
http://www.novell.com/linux/security/advisories/2003_003_mysql.html	vendor advisory
http://www.redhat.com/support/errata/RHSA-2002-289.html	vendor advisory
http://www.trustix.net/errata/misc/2002/TSL-2002-0086-mysql.asc.txt	vendor advisory
http://www.securityfocus.com/bid/6373	patch vendor advisory vdb entry exploit
http://www.securityfocus.com/advisories/5269	vendor advisory

Frequently Asked Questions

What is the severity of CVE-2002-1374?: CVE-2002-1374 has been scored as a high severity vulnerability.
How to fix CVE-2002-1374?: To fix CVE-2002-1374, 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-2002-1374 being actively exploited in the wild?: It is possible that CVE-2002-1374 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~25% probability that this vulnerability will be exploited by malicious actors in the next 30 days.