Loading vulnerability…
A stack-based buffer overflow exists in the CertDecoder::GetName function in src/asn.cpp within the TaoCrypt component of yaSSL before 1.9.9. This vulnerability is triggered when a remote attacker establishes an SSL connection to a service (such as mysqld in MySQL 5.0.x before 5.0.90, 5.1.x before 5.1.43, and 5.5.x through 5.5.0-m2) and presents a specially crafted X.509 client certificate with a maliciously constructed name field. The overflow occurs due to insufficient bounds checking when copying the name field, leading to memory corruption.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a single Metasploit module (modules/exploits/linux/mysql/mysql_yassl_getname.rb) that exploits a stack buffer overflow vulnerability in the yaSSL library (version 1.9.8 and earlier) as used by MySQL. The exploit targets the CertDecoder::GetName function in the yaSSL code, specifically in taocrypt/src/asn.cpp. By sending a specially crafted client certificate during the SSL handshake, the attacker can trigger a buffer overflow and execute arbitrary code on the target system. The exploit is operational and allows for custom shellcode payloads. It targets MySQL servers running on Linux, specifically those using yaSSL and configured for SSL connections, and requires the attacker to have network access and pass host-based authentication. The default target port is 3306. The repository is a part of the Metasploit framework and is structured as a typical Metasploit exploit module.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.