CVE-2009-4484

CVE-2009-4484 is a high-severity vulnerability in Oracle Mysql with a CVSS 2.0 base score of 7.5. Its EPSS exploit-prediction score of 70% places it in the 99th percentile, indicating an elevated likelihood of exploitation. The underlying weakness is classified as CWE-787.

Key facts

Description

Multiple stack-based buffer overflows in the CertDecoder::GetName function in src/asn.cpp in TaoCrypt in yaSSL before 1.9.9, as used in mysqld in MySQL 5.0.x before 5.0.90, MySQL 5.1.x before 5.1.43, MySQL 5.5.x through 5.5.0-m2, and other products, allow remote attackers to execute arbitrary code or cause a denial of service (memory corruption and daemon crash) by establishing an SSL connection and sending an X.509 client certificate with a crafted name field, as demonstrated by mysql_overflow1.py and the vd_mysql5 module in VulnDisco Pack Professional 8.11. NOTE: this was originally reported for MySQL 5.0.51a.

Frequently asked questions

What is CVE-2009-4484?
Multiple stack-based buffer overflows in the CertDecoder::GetName function in src/asn.cpp in TaoCrypt in yaSSL before 1.9.9, as used in mysqld in MySQL 5.0.x before 5.0.90, MySQL 5.1.x before 5.1.43, MySQL 5.5.x through 5.5.0-m2, and other products, allow remote attackers to execute arbitrary code or cause a denial of service (memory corruption and daemon crash) by establishing an SSL connection and sending an X.509 client certificate with a crafted name field, as demonstrated by mysql_overflow1.py and the vd_mysql5 module in VulnDisco Pack Professional 8.11. NOTE: this was originally reported for MySQL 5.0.51a.
How severe is CVE-2009-4484?
CVE-2009-4484 has a CVSS 2.0 base score of 7.5, rated high severity.
Is CVE-2009-4484 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 70% (99th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2009-4484?
CVE-2009-4484 primarily affects Oracle Mysql. In total, 17 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2009-4484?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2009-4484 published?
CVE-2009-4484 was published on 2009-12-30 and last updated on 2026-06-16.

References

Affected products (17)

More vulnerabilities in Oracle Mysql

All CVEs affecting Oracle Mysql →

Other CWE-787 (Out-of-bounds Write) vulnerabilities

Browse all CWE-787 (Out-of-bounds Write) vulnerabilities →