CVE-2002-1923: High severity ORACLE MySQL vulnerability
The default configuration in MySQL 3.20.32 through 3.23.52, when running on Windows, does not have logging enabled, which could allow remote attackers to conduct activities without detection.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Configuration
Enable logging for the MySQL server on Windows installations of versions 3.20.32 through 3.23.52 by configuring the server's configuration file (e.g., my.ini) to turn on logging so that server activities are recorded and can be detected.
MySQL (3.20.32 through 3.23.52 on Windows) logging = enabled
Event History
Frequently Asked Questions
What is the severity of CVE-2002-1923?
CVE-2002-1923 is considered a high-severity vulnerability due to the lack of logging, which enables undetected malicious activities.
How do I fix CVE-2002-1923?
To fix CVE-2002-1923, enable logging in the MySQL configuration for affected versions.
What software versions are affected by CVE-2002-1923?
CVE-2002-1923 affects MySQL versions 3.20.32 to 3.23.52 on Windows systems.
Can CVE-2002-1923 be exploited remotely?
Yes, CVE-2002-1923 can be exploited by remote attackers due to the absence of logging.
What are the consequences of not addressing CVE-2002-1923?
Not addressing CVE-2002-1923 may result in unauthorized actions on the MySQL database that go unnoticed.