Skip to content
Fencer Vulns
high 7.5

CVE-2002-1374 in the critical feed json

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…

published 2002-12-23 23 y ago modified 2026-06-16 4 mo ago also EUVD-2002-1358

cvss
7.5
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
20.5%
EPSS 20.5% chance of exploitation in 30 days, percentile 97%
public exploits
1
Exploit-DB

Summary

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.

Patch / fix

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2002-1374 updated

security flaw

  • Red Hat Linux 7.0 Red Hat Linux 7.1 Red Hat Linux 7.2 Red Hat Linux 7.3 Red Hat Linux 8.0
    fixed: vendor fix RHSA-2002:288
  • Red Hat Linux Advanced Workstation 2.1
    fixed: vendor fix RHSA-2002:289

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Timeline

  1. First public exploit (EDB-22084)
  2. Published

Exploit prediction

20.45% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • EDB-22084 MySQL 3.23.x/4.0.x - 'COM_CHANGE_USER' Password Length Account remote, 2002-12-16
  • securityfocus.com http://www.securityfocus.com/bid/6373 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P

Classification

Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.