MySQLDatabase / datastore · Oracle
CVE-2005-2572
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMySQL, when running on Windows, allows remote authenticated users with insert privileges on the mysql.func table to cause a denial of service (server hang) and possibly execute arbitrary code via (1) a request for a non-library file, which causes the Windows LoadLibraryEx function to block, or (2) a request for a function in a library that has the XXX_deinit or XXX_init functions defined but is not tailored for mySQL, such as jpeg1x32.dll and jpeg2x32.dll.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceMySQL on Windows contains a vulnerability in its User-Defined Function (UDF) loading mechanism. Authenticated users with INSERT privileges on the mysql.func table can specify arbitrary DLL files to be loaded via MySQL's use of Windows LoadLibraryEx. Attackers can either cause denial of service by specifying non-library files (which blocks LoadLibraryEx), or potentially execute arbitrary code by loading DLLs with XXX_init or XXX_deinit functions not designed for MySQL's UDF interface.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
MySQLDatabase / datastore
= 5.0.33CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- M
- Authentication
- Single
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:M/Au:S/C:C/I:C/A:C
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify MySQL versionRun 'mysql --version' or 'SELECT VERSION();' from a MySQL client to confirm the installed version is 5.0.33Affected if The installed version is exactly 5.0.33 on Windows
-
Confirm Windows platformCheck the operating system where MySQL is running - this vulnerability only affects MySQL on Windows platformsAffected if MySQL server is running on Windows operating system
-
Check for INSERT privilege on mysql.funcExecute 'SELECT user, host FROM mysql.func;' while logged in as a user with privileges to query the mysql database, or ask an administrator to check which users have INSERT privilege on the mysql.func table using 'SHOW GRANTS FOR user@host;'Affected if Any database user has INSERT privilege on the mysql.func table (other than trusted admin accounts)
-
Verify UDF loading capabilityCheck if the mysql.func table exists and contains entries, or test if non-admin users can query the mysql.func table structure using 'DESCRIBE mysql.func;'Affected if The mysql.func table is accessible and users with INSERT privileges can potentially add rows to it
A user is affected if MySQL 5.0.33 is running on Windows and any non-administrative user has INSERT privileges on the mysql.func table, allowing them to load arbitrary DLLs via the UDF mechanism.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataRestrict INSERT privileges on the mysql.func table to only trusted administrative accounts; follow least-privilege principles for database users; consider upgrading to a patched MySQL version if available.
Fix this in MySQL
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2005-2572 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2005-2572 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data