Skip to content
Fencer Vulns
medium 4.6

CVE-2005-1636 json

mysql_install_db in MySQL 4.1.x before 4.1.12 and 5.x up to 5.0.4 creates the mysql_install_db.X file with a predictable filename and insec…

published 2005-05-17 21 y ago modified 2026-06-16 4 mo ago also EUVD-2005-1638

cvss
4.6
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.6%
EPSS 0.6% chance of exploitation in 30 days, percentile 49%
public exploits
0
none known

Summary

mysql_install_db in MySQL 4.1.x before 4.1.12 and 5.x up to 5.0.4 creates the mysql_install_db.X file with a predictable filename and insecure permissions, which allows local users to execute arbitrary SQL commands by modifying the file's contents.

Patch / fix

  • mysql RHEL 4 4.1.12-3.RHEL4.1
  • mysql-bench RHEL 4 4.1.12-3.RHEL4.1
  • mysql-server RHEL 4 4.1.12-3.RHEL4.1

red hat advisories RHSA-2005:685

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-2005-1636 updated

security flaw

  • Red Hat Enterprise Linux AS version 4 mysql 4.1.12-3.RHEL4.1, mysql-bench 4.1.12-3.RHEL4.1, mysql-server 4.1.12-3.RHEL4.1 Red Hat Enterprise Linux Desktop version 4 mysql 4.1.12-3.RHEL4.1, mysql-bench 4.1.12-3.RHEL4.1, mysql-server 4.1.12-3.RHEL4.1 Red Hat Enterprise Linux ES version 4 mysql 4.1.12-3.RHEL4.1, mysql-bench 4.1.12-3.RHEL4.1, mysql-server 4.1.12-3.RHEL4.1 Red Hat Enterprise Linux WS version 4 mysql 4.1.12-3.RHEL4.1, mysql-bench 4.1.12-3.RHEL4.1, mysql-server 4.1.12-3.RHEL4.1
    fixed: vendor fix RHSA-2005:685

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

Exploit prediction

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

CVSS scores

assigned by version score vector
NVD 2.0 4.6 AV:L/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.