How severe is CVE-2004-0837?

CVE-2004-0837 has a CVSS 2.0 base score of 2.6, rated low severity.

Is CVE-2004-0837 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 5% (91st percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2004-0837?

CVE-2004-0837 primarily affects Mysql. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2004-0837?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2004-0837 published?

CVE-2004-0837 was published on 2004-11-03 and last updated on 2026-06-16.

CVE-2004-0837

CVE-2004-0837 is a low-severity vulnerability in Mysql with a CVSS 2.0 base score of 2.6. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Low (CVSS 2.0 base score 2.6)
EPSS exploit prediction: 5% (91st percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Mysql
Published: 2004-11-03
Last modified: 2026-06-16

Description

MySQL 4.x before 4.0.21, and 3.x before 3.23.49, allows attackers to cause a denial of service (crash or hang) via multiple threads that simultaneously alter MERGE table UNIONs.

Frequently asked questions

What is CVE-2004-0837?: MySQL 4.x before 4.0.21, and 3.x before 3.23.49, allows attackers to cause a denial of service (crash or hang) via multiple threads that simultaneously alter MERGE table UNIONs.
How severe is CVE-2004-0837?: CVE-2004-0837 has a CVSS 2.0 base score of 2.6, rated low severity.
Is CVE-2004-0837 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 5% (91st percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2004-0837?: CVE-2004-0837 primarily affects Mysql. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2004-0837?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2004-0837 published?: CVE-2004-0837 was published on 2004-11-03 and last updated on 2026-06-16.

References

Affected products (3)

cpe:2.3:a:mysql:mysql:4.1.0:*:*:*:*:*:*:*
cpe:2.3:a:oracle:mysql:*:*:*:*:*:*:*:*
cpe:2.3:o:debian:debian_linux:3.0:*:*:*:*:*:*:*

More vulnerabilities in Mysql

CVE-2004-0627 — Critical (CVSS 10.0): The check_scramble_323 function in MySQL 4.1.x before 4.1.3, and 5.0, allows remote attackers to bypass authentication…
CVE-2004-0628 — Critical (CVSS 10.0): Stack-based buffer overflow in MySQL 4.1.x before 4.1.3, and 5.0, allows remote attackers to cause a denial of service…
CVE-2003-0780 — Critical (CVSS 9.0): Buffer overflow in get_salt_from_password from sql_acl.cc for MySQL 4.0.14 and earlier, and 3.23.x, allows attackers…
CVE-2009-2446 — High (CVSS 8.5): Multiple format string vulnerabilities in the dispatch_command function in libmysqld/sql_parse.cc in mysqld in MySQL…
CVE-2017-15945 — High (CVSS 7.8): The installation scripts in the Gentoo dev-db/mysql, dev-db/mariadb, dev-db/percona-server, dev-db/mysql-cluster, and…
CVE-2013-1492 — High (CVSS 7.5): Buffer overflow in yaSSL, as used in MySQL 5.1.x before 5.1.68 and 5.5.x before 5.5.30, has unspecified impact and…

All CVEs affecting Mysql →