dbcve.org
MySQLDatabase / datastore

CVE-2008-0226

HIGH · 7.5 CVSS v2.0 Published 2008-01-10
Fix available
A fix is available. Upgrade to after 1.7.5 or later.
See remediation →
84/100
Remediation priority · High
High EPSS Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Buffer overflow vulnerability in yaSSL versions 1.7.5 and earlier allows remote attackers to execute arbitrary code via malformed SSL handshake messages. Two specific locations are vulnerable: the ProcessOldClientHello function in handshake.cpp and the input_buffer operator>> in yassl_imp.cpp. This yaSSL library is used by MySQL and potentially other products.

MitigationUpgrade yaSSL to a version newer than 1.7.5, or upgrade affected products (such as MySQL) to versions that include the patched yaSSL library. Consider network segmentation to limit exposure to SSL/TLS services until patching can be completed.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
MySQLDatabase / datastore
Affected:= 5.0.0= 5.0.1= 5.0.2= 5.0.3= 5.0.4= 5.0.5= 5.0.10= 5.0.15= 5.0.16= 5.0.17= 5.0.20= 5.0.24
MySQLDatabase / datastore
Affected:= 5.0.23= 5.0.25= 5.0.26= 5.0.28= 5.0.30= 5.0.32= 5.0.34= 5.0.36= 5.0.38= 5.0.40= 5.0.41= 5.0.42
Debian LinuxOperating system
Affected:= 5.0
Ubuntu LinuxOperating system
Affected:= 6.06= 6.10= 7.04= 7.10
YasslApplication
Affected:<= 1.7.5
Mac Os XOperating system
Affected:= 10.5.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:N/C:P/I:P/A:P

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify MySQL version
    Run 'mysql --version' or 'SELECT VERSION();' query to get the installed MySQL version
    Affected if Version matches any of the listed affected versions (5.0.0-5.0.42 range, specific versions listed)
  2. Check if yaSSL library is present
    Locate yaSSL library files - common paths include /usr/lib/, /usr/local/lib/, or check MySQL compiled binaries with 'ldd' or 'strings' for yaSSL references
    Affected if yaSSL library version is 1.7.5 or earlier, or MySQL binary references vulnerable yaSSL code
  3. Verify SSL/TLS is enabled in MySQL
    Check MySQL configuration (my.cnf) for 'ssl' or 'SSL' directives, or run 'SHOW VARIABLES LIKE "%ssl%";' query to see if SSL is enabled
    Affected if SSL is enabled (have_ssl or ssl_type variable shows SSL is active) - the vulnerability only triggers when SSL handshake processing occurs
  4. Check operating system version
    Run 'uname -a' or check /etc/lsb-release (Ubuntu) /etc/debian_version (Debian) /sw/Version.plist (Mac OS X) for OS version
    Affected if Running Debian 5.0, Ubuntu 6.06, 6.10, 7.04, 7.10, or Mac OS X 10.5.4 with vulnerable yaSSL
  5. Confirm yaSSL version directly
    Check yaSSL library file version: run 'yassl --version' if CLI tool exists, or check library file metadata with 'file' and 'strings' commands for version strings
    Affected if yaSSL version is 1.7.5 or earlier

You are affected if your MySQL version is in the affected 5.0.x list, or your yaSSL library is version 1.7.5 or earlier, AND SSL/TLS is enabled and exposed to network connections.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 1.7.5
Interim mitigation

Upgrade yaSSL to a version newer than 1.7.5, or upgrade affected products (such as MySQL) to versions that include the patched yaSSL library. Consider network segmentation to limit exposure to SSL/TLS services until patching can be completed.

Fix this in MySQL Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2008-0226 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2008-0226 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data