CVE-2002-1374: High severity Symantec Veritas Netbackup Global Data Manager vulnerability

Published Dec 23, 2002
·
Updated

The COMCHANGEUSER 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.

Affected Software

62 affected components
Symantec Veritas Netbackup Global Data Manager=4.5_mp2
Symantec Veritas Netbackup Global Data Manager=4.5_fp2
Symantec Veritas Netbackup Global Data Manager=4.5_fp1
Symantec Veritas Netbackup Global Data Manager=4.5_fp3
Symantec Veritas Netbackup Advanced Reporter=4.5_fp2
Symantec Veritas Netbackup Advanced Reporter=4.5_fp1
Symantec Veritas Netbackup Advanced Reporter=4.5_mp1
Symantec Veritas Netbackup Advanced Reporter=4.5_fp3
Symantec Veritas Netbackup Global Data Manager=4.5_mp1
Symantec Veritas Netbackup Advanced Reporter=4.5_mp3
Symantec Veritas Netbackup Global Data Manager=4.5_mp3
Symantec Veritas Netbackup Advanced Reporter=3.4
Symantec Veritas Netbackup Advanced Reporter=4.5
Symantec Veritas Netbackup Global Data Manager=4.5
Symantec Veritas Netbackup Advanced Reporter=4.5_mp2
ORACLE MySQL=3.22.26
ORACLE MySQL=3.22.27
ORACLE MySQL=3.22.28
ORACLE MySQL=3.22.29
ORACLE MySQL=3.22.30
ORACLE MySQL=3.22.32
ORACLE MySQL=3.23.2
ORACLE MySQL=3.23.3
ORACLE MySQL=3.23.4
ORACLE MySQL=3.23.5
ORACLE MySQL=3.23.8
ORACLE MySQL=3.23.9
ORACLE MySQL=3.23.10
ORACLE MySQL=3.23.23
ORACLE MySQL=3.23.24
ORACLE MySQL=3.23.25
ORACLE MySQL=3.23.26
ORACLE MySQL=3.23.27
ORACLE MySQL=3.23.28
ORACLE MySQL=3.23.29
ORACLE MySQL=3.23.30
ORACLE MySQL=3.23.31
ORACLE MySQL=3.23.34
ORACLE MySQL=3.23.36
ORACLE MySQL=3.23.37
ORACLE MySQL=3.23.38
ORACLE MySQL=3.23.39
ORACLE MySQL=3.23.40
ORACLE MySQL=3.23.41
ORACLE MySQL=3.23.42
ORACLE MySQL=3.23.43
ORACLE MySQL=3.23.44
ORACLE MySQL=3.23.45
ORACLE MySQL=3.23.46
ORACLE MySQL=3.23.47
ORACLE MySQL=3.23.48
ORACLE MySQL=3.23.49
ORACLE MySQL=3.23.50
ORACLE MySQL=3.23.51
ORACLE MySQL=3.23.52
ORACLE MySQL=3.23.53
ORACLE MySQL=3.23.53a
ORACLE MySQL=4.0.0
ORACLE MySQL=4.0.1
ORACLE MySQL=4.0.2
ORACLE MySQL=4.0.3
ORACLE MySQL=4.0.5a

Event History

Dec 23, 2002
CVE Published
05:00 AM
Sep 1, 2004
CVE Published
via MITRE·08:00 AM
Data Sourced
via MITRE·08:00 AM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2002-1374?

CVE-2002-1374 is considered to be a high severity vulnerability due to the potential for unauthorized access.

2

How do I fix CVE-2002-1374?

To fix CVE-2002-1374, upgrade your MySQL version to 3.23.54 or later, or 4.0.6 or later.

3

What systems are affected by CVE-2002-1374?

CVE-2002-1374 affects MySQL versions 3.x prior to 3.23.54 and 4.x prior to 4.0.6.

4

Can CVE-2002-1374 be exploited remotely?

Yes, CVE-2002-1374 can be exploited remotely using a brute force attack with a one-character password.

5

What is the impact of CVE-2002-1374?

The impact of CVE-2002-1374 is that it allows remote attackers to gain privileges on the affected MySQL server.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203