CVE-2001-1255
First published: Tue Oct 02 2001(Updated: )
WinMySQLadmin 1.1 stores the MySQL password in plain text in the my.ini file, which allows local users to obtain unathorized access the MySQL database.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| MySQL | =1.1 | |
| Oracle MySQL | =3.23 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2001-1255?
The severity of CVE-2001-1255 is considered high due to the risk of unauthorized access to the MySQL database.
How do I fix CVE-2001-1255?
To fix CVE-2001-1255, change the MySQL password storage method to secure hashing instead of storing it in plain text in the my.ini file.
Who is affected by CVE-2001-1255?
CVE-2001-1255 affects users of WinMySQLadmin version 1.1 and MySQL version 3.23.
What are the potential impacts of CVE-2001-1255?
The potential impacts of CVE-2001-1255 include unauthorized access to sensitive database information and possible data breaches.
Is CVE-2001-1255 a remote or local vulnerability?
CVE-2001-1255 is a local vulnerability, requiring an attacker to have local access to the system hosting the MySQL database.
- agent/type
- agent/first-publish-date
- collector/mitre-cve
- source/MITRE
- agent/weakness
- agent/author
- agent/severity
- agent/references
- agent/last-modified-date
- agent/description
- agent/event
- agent/source
- agent/tags
- agent/softwarecombine
- collector/nvd-index
- agent/software-canonical-lookup-request
- collector/nvd-historical
- vendor/mysql
- canonical/mysql
- version/mysql/1.1
- vendor/oracle
- canonical/oracle mysql
- version/oracle mysql/3.23