CVE-2009-4484: n/a vulnerability

CVE-2009-4484: Multiple stack-based buffer overflows in the CertDecoder::GetName function in src/asn.cpp in TaoCrypt in ya...

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.

UnknownCVSS not scoredNot KEV-listedUpdatedAug 7, 2024, 07:01 UTC (UTC+00:00)

Security readout for executives and security teams

This flaw affected older MySQL builds using yaSSL/TaoCrypt. A remote attacker could crash the database daemon or potentially run code by presenting a malformed X.509 client certificate during an SSL connection. The main business risk is legacy internet- or partner-facing MySQL services that still run the vulnerable versions. Exposure is most likely in legacy MySQL 5.0.x before 5.0.90, 5.1.x before 5.1.43, 5.5.x through 5.5.0-m2, or other products embedding yaSSL before 1.9.9. Prioritize remediation for any remaining legacy MySQL service exposed beyond tightly trusted networks. Modern supported builds are unlikely to be affected, but old database servers can persist unnoticed and carry high-impact memory-corruption risk. Mitigation focus: Upgrade MySQL to a fixed vendor-supported release.; Upgrade embedded yaSSL/TaoCrypt to yaSSL 1.9.9 or later.; Prioritize systems accepting SSL connections from untrusted networks..

Prepared: Jun 28, 2026, 09:59 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup

cve · low confidence lookup

CVE-2009-4484 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup

Vulnerability profileCVE Program record

Severity: Unknown
CVSS: Not scored
Known Exploited: No
Published: Dec 30, 2009, 21:00 UTC (UTC+00:00)

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors

0Timeline events

0ADP providers

3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

CVE List V5 sourceCVE List V5
https://bugzilla.redhat.com/show_bug.cgi?id=555313CVE reference · x_refsource_CONFIRM
mysql-unspecified-bo(55416)CVE reference · vdb-entry, x_refsource_XF

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus

n/an/an/aListed

Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.