Multiple buffer overflows in yaSSL 1.7.5 and earlier, as used in MySQL and possibly other products, allow remote attackers to execute arbitrary code via (1) the ProcessOldClientHello function in handshake.cpp or (2) "input_buffer& operator>>" in yassl_imp.cpp.
CVE-2008-0226
HIGHCVSS v2 · 7.57.5WeaponizedEG-KEV Tier 2: WeaponizedEG-KEV is EchelonGraph's own tiering of exploitation signals from CISA KEV, CISA's SSVC data (Vulnrichment), ransomware data, public exploit-code references and EPSS.Tier 2 is not evidence of exploitation. It means a Metasploit module exists, or Exploit-DB marks a public exploit verified, or CISA's SSVC data says "public PoC" and EPSS is 50% or more. EchelonGraph does not test whether exploit code works.Signals for this CVE: a Metasploit module, an Exploit-DB entry Exploit-DB marks verified, EPSS in the top 5%, EPSS 50% or more.Earliest public exploit code on record: 2008-01-04 (Exploit-DB EDB-9953)EchelonGraph confidence 70%: a heuristic from the tier and the number of signals, not a measured probability.
EchelonGraph scoreLOW confidence
“—” beside the score: it is equal to NVD's CVSS v2 base score.
This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 7.5 — NVD rates that HIGH (NVD's v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; no CRITICAL band). Vector AV:N/AC:L/Au:N/C:P/I:P/A:P. CVSS v2 is an older, coarser metric than v3.1/v4.0 (no Scope, no User Interaction, no Attack Requirements), so it is not directly comparable to a v3 or v4 score. NVD has never re-scored this record under v3. EPSS predicts 92% exploitation probability in the next 30 days; it does not lift the v2 base. EPSS sets EG Risk's exploitation input. Confidence: LOW.
Triggered by: NVD CVSS v2.0 (legacy fallback)
Sources: NVD CVSS v2.0
7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
- High exploitation likelihood — EPSS 92%
- Public exploit code is available (Metasploit, Exploit-DB, marked verified by Exploit-DB)
CISA-KEV: Not listedEPSS PROB: 92%CVSS v2: 7.5Exploit: Metasploit · Exploit-DB (verified)Exposed services: Not assessed
A fix is available — apply it.
- CVSS v2.0 (legacy)
- 7.5HIGHNVD never assigned a CVSS v3 rating to this CVE
- EG Score
- 7.5HIGHlow confidence
- EG Risk
- 70EG Risk 70/100
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computed (value × EchelonGraph’s weight)Severity75% × 45%The EG Score, 7.5 of 10.Exploitation92% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability0% × 15%CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.Exploitation public PoC (exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 92%
- EPSS %ILE
- 99th
- KEV
- Not listed
SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation public PoC (exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
January 10, 2008
Last Modified
April 23, 2026
References (21)
- MITRE · CVE Programhttp://bugs.mysql.com/33814Permissions Required
- MITRE · CVE Programhttp://dev.mysql.com/doc/refman/5.1/en/news-5-1-23.htmlNot Applicable
- MITRE · CVE Programhttp://lists.apple.com/archives/security-announce/2008/Oct/msg00001.htmlMailing List · Third Party Advisory
- MITRE · CVE Programhttp://secunia.com/advisories/28324 (archived copy: the site no longer serves it)Not Applicable
- MITRE · CVE Programhttp://secunia.com/advisories/28419 (archived copy: the site no longer serves it)Not Applicable
- MITRE · CVE Programhttp://secunia.com/advisories/28597 (archived copy: the site no longer serves it)Not Applicable
- MITRE · CVE Programhttp://secunia.com/advisories/29443 (archived copy: the site no longer serves it)Not Applicable
- MITRE · CVE Programhttp://secunia.com/advisories/32222 (archived copy: the site no longer serves it)Not Applicable
- MITRE · CVE Programhttp://securityreason.com/securityalert/3531Third Party Advisory
- MITRE · CVE Programhttp://support.apple.com/kb/HT3216Third Party Advisory
- MITRE · CVE Programhttp://www.debian.org/security/2008/dsa-1478Third Party Advisory
- MITRE · CVE Programhttp://www.mandriva.com/security/advisories?name=MDVSA-2008:150Broken Link
- MITRE · CVE Programhttp://www.securityfocus.com/archive/1/485810/100/0/threaded (archived copy: the site no longer serves it)Third Party Advisory · VDB Entry
- MITRE · CVE Programhttp://www.securityfocus.com/archive/1/485811/100/0/threaded (archived copy: the site no longer serves it)Third Party Advisory · VDB Entry
- MITRE · CVE Programhttp://www.securityfocus.com/bid/27140 (archived copy: the site no longer serves it)Third Party Advisory · VDB Entry
15 of 21 shown · show the other 6
- MITRE · CVE Programhttp://www.securityfocus.com/bid/31681 (archived copy: the site no longer serves it)Third Party Advisory · VDB Entry
- MITRE · CVE Programhttp://www.ubuntu.com/usn/usn-588-1Third Party Advisory
- MITRE · CVE Programhttp://www.vupen.com/english/advisories/2008/0560/referencesPermissions Required
- MITRE · CVE Programhttp://www.vupen.com/english/advisories/2008/2780Permissions Required
- MITRE · CVE Programhttps://exchange.xforce.ibmcloud.com/vulnerabilities/39429VDB Entry
- MITRE · CVE Programhttps://exchange.xforce.ibmcloud.com/vulnerabilities/39431VDB Entry
Patch Availability(1)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| ubuntu | mysql-server-5.0 (5.0.45-1ubuntu3.3) @ gutsy | 2026-07-23 | ubuntu |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(1 across 1 ecosystem)
Debian:4.0(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| mysql-dfsg-5.0 | 5.0.32-7etch1, 5.0.32-7etch3, 5.0.32-7etch3~bpo31+1, 5.0.32-7etch4, 5.0.32-7etch5~bpo31+1 |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
All Vendor Advisories
(1)
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
Data Freshness Timeline
(refreshed 2× in last 7d / 4× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 19 repeat rows among the latest 66 are merged into the row they repeat.
- 2026-10-12 02:02 UTCEG score recompute
- 2026-10-06 15:09 UTCEPSS rescoreEPSS 92% · 99th percentile
- 2026-09-29 07:46 UTCEG score recompute
- 2026-09-18 19:20 UTCEPSS rescoreEPSS 92% · 99th percentile
- 2026-09-05 15:22 UTCEPSS rescoreEPSS 92% · 99th percentile
- 2026-09-04 13:55 UTCEPSS rescoreEPSS 92% · 99th percentile
- 2026-09-04 04:59 UTCEPSS rescoreEPSS 92% · 99th percentile
- 2026-08-08 16:30 UTCEPSS rescoreEPSS 92% · 99th percentile
- 2026-08-05 19:11 UTCEPSS rescoreEPSS 92% · 99th percentile
- 2026-07-30 01:25 UTCEPSS rescoreEPSS 92% · 99th percentile
- 2026-07-26 13:34 UTCEG score recomputeAssessed again: 7.5 HIGH
- 2026-07-24 14:11 UTCEPSS rescoreEPSS 92% · 99th percentile
- 2026-07-23 00:55 UTCEG score recompute
- 2026-07-23 00:39 UTCVendor advisory
- 2026-07-23 00:39 UTCGHSA enrichmentGHSA-62p8-jm49-f9f2 · GitHub severity HIGH
- 2026-07-23 00:36 UTCVendor advisory
- 2026-07-23 00:36 UTCGHSA enrichmentGHSA-62p8-jm49-f9f2 · GitHub severity HIGH
- 2026-07-23 00:36 UTCGHSA enrichmentGHSA-62p8-jm49-f9f2 · GitHub severity HIGH
- 2026-07-23 00:34 UTCGHSA enrichmentGHSA-62p8-jm49-f9f2 · GitHub severity HIGH
- 2026-07-23 00:34 UTCEG score recompute▼ 9.00
- 2026-07-23 00:00 UTCEG score recompute
- 2026-07-22 21:39 UTCEG score recompute
- 2026-07-22 14:03 UTCEPSS rescoreEPSS 92% · 99th percentile
- 2026-07-15 16:54 UTCEPSS rescoreEPSS 92% · 99th percentile
- 2026-07-04 06:27 UTCEPSS rescoreEPSS 92% · 99th percentile
Show 22 moreShow fewer
- 2026-06-30 23:19 UTCEPSS rescoreEPSS 92% · 99th percentile
- 2026-06-29 14:02 UTCEPSS rescoreEPSS 92% · 99th percentile
- 2026-06-28 14:03 UTCEPSS rescoreEPSS 92% · 99th percentile
- 2026-06-24 14:02 UTCEPSS rescoreEPSS 92% · 99th percentile
- 2026-06-23 21:29 UTCEPSS rescoreEPSS 92% · 99th percentile
- 2026-06-16 17:49 UTCEPSS rescoreEPSS 92% · 99th percentile
- 2026-06-15 17:44 UTCEPSS rescoreEPSS 92% · 99th percentile
- 2026-06-12 23:08 UTCEPSS rescoreEPSS 92% · 99th percentile
- 2026-06-07 15:21 UTCEPSS rescoreEPSS 92% · 99th percentile
- 2026-06-06 13:44 UTCEPSS rescoreEPSS 92% · 99th percentile
- 2026-06-05 06:07 UTCEPSS rescoreEPSS 92% · 99th percentile
- 2026-06-01 13:49 UTCEPSS rescoreEPSS 92% · 99th percentile
- 2026-05-31 22:28 UTCEPSS rescoreEPSS 92% · 99th percentile
- 2026-05-30 23:25 UTCEG score recompute
- 2026-05-30 23:25 UTCVendor advisory
- 2026-05-30 23:25 UTCGHSA enrichmentGHSA-62p8-jm49-f9f2 · GitHub severity HIGH
- 2026-05-29 13:40 UTCEPSS rescoreEPSS 92% · 99th percentile
- 2026-05-28 13:42 UTCEPSS rescoreEPSS 92% · 99th percentile
- 2026-05-27 13:37 UTCEPSS rescoreEPSS 92% · 99th percentile
- 2026-05-26 07:16 UTCEPSS rescoreEPSS 92% · 99th percentile
- 2026-05-20 22:36 UTCEPSS rescoreEPSS 92% · 99th percentile
- 2026-05-18 21:29 UTCEPSS rescoreEPSS 92% · 99th percentile
Publicly available exploits
(5 references)Public exploit code is referenced for this CVE (2 Metasploit modules, 3 Exploit-DB entries). Defenders should treat patch urgency accordingly.
- Exploit-DBEDB-16701✓ verifiedPublished May 9, 2010
MySQL yaSSL (Windows) - SSL Hello Message Buffer Overflow (Metasploit)
Open source ↗ - Exploit-DBEDB-16849✓ verifiedPublished May 9, 2010
MySQL yaSSL (Linux) - SSL Hello Message Buffer Overflow (Metasploit)
Open source ↗ - Metasploitexploit/windows/mysql/mysql_yassl_hello✓ verifiedPublished Jan 26, 2010
MySQL yaSSL SSL Hello Message Buffer Overflow
Open source ↗ - Metasploitexploit/linux/mysql/mysql_yassl_hello✓ verifiedPublished Apr 1, 2008
MySQL yaSSL SSL Hello Message Buffer Overflow
Open source ↗ - Exploit-DBEDB-9953✓ verifiedPublished Jan 4, 2008
MySQL 6.0 yaSSL 1.7.5 - Hello Message Buffer Overflow (Metasploit)
Open source ↗
Related CVEs(same product + same vendor + same CWE)
Same product
10 shownDebian:4.0:mysql-dfsg-5.0
Same vendor
4 shownubuntu:USN-588-1
Same CWE
10 shownCWE-119
Frequently asked(4)
What is CVE-2008-0226?
CVE-2008-0226 is a high-severity vulnerability; its CVE record was published on January 10, 2008. Multiple buffer overflows in yaSSL 1.7.5 and earlier, as used in MySQL and possibly other products, allow remote attackers to execute arbitrary code via (1) the ProcessOldClientHello function in handshake.cpp or (2) "inputbuffer& operator>>" in yasslimp.cpp.
When was CVE-2008-0226 made public?
CVE-2008-0226 was made public on January 4, 2008: that is the date its CVE record's CNA, MITRE Corporation, gives for when the vulnerability was made public. The CVE record itself was published on January 10, 2008. EchelonGraph's copy of the record carries a last-modified date of April 23, 2026; the record at its source may have been updated since.
Is CVE-2008-0226 actively exploited?
CVE-2008-0226 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model places it in Tier 2 (Weaponized), which is not evidence of exploitation: a Metasploit module exists for it, and Exploit-DB marks a public exploit for it as verified. EchelonGraph does not test whether exploit code works. FIRST EPSS estimates a 92% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
How do I remediate CVE-2008-0226?
A fix for CVE-2008-0226 is available: update to the fixed version the vendor names in its advisory.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2008-0226
Is Your Infrastructure Affected by CVE-2008-0226?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.