Skip to content
Fencer Vulns
high 7.5

CVE-2004-0835 in the critical feed json

MySQL 3.x before 3.23.59, 4.x before 4.0.19, 4.1.x before 4.1.2, and 5.x before 5.0.1, checks the CREATE/INSERT rights of the original tabl…

published 2004-10-16 22 y ago modified 2026-06-16 4 mo ago also EUVD-2004-0833

cvss
7.5
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
22.4%
EPSS 22.4% chance of exploitation in 30 days, percentile 97%
public exploits
1
Exploit-DB

Summary

MySQL 3.x before 3.23.59, 4.x before 4.0.19, 4.1.x before 4.1.2, and 5.x before 5.0.1, checks the CREATE/INSERT rights of the original table instead of the target table in an ALTER TABLE RENAME operation, which could allow attackers to conduct unauthorized activities.

Patch / fix

  • oracle mysql 3.23.59, 4.0.19

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-2004-0835 updated

security flaw

  • Red Hat Desktop version 3 Extras
    fixed: vendor fix RHSA-2004:611
  • Red Hat Enterprise Linux ES version 2.1 Red Hat Enterprise Linux WS version 2.1 Red Hat Linux Advanced Workstation 2.1
    fixed: vendor fix RHSA-2004:597

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

Timeline

  1. First public exploit (EDB-24669)
  2. Published

Exploit prediction

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

Exploits and checks

  • EDB-24669 MySQL 3.x/4.x - ALTER TABLE/RENAME Forces Old Permission Checks remote, 2004-10-08
  • securityfocus.com http://www.securityfocus.com/bid/11357 referenced PoC, tagged "exploit" by a source, unverified
  • bugs.mysql.com http://bugs.mysql.com/bug.php?id=3270 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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