Sign inStart freeBook a demo

What is CVE-2009-4484?A high-severity flaw in MySQL, explained.

High severity5 affected products
The short answer

CVE-2009-4484 is a high-severity flaw (CVSS 7.5) in MySQL from Oracle, published on 30 December 2009. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 70%. If you run an affected version, plan in the vendor’s fix.

Check if it affects you →How to fix it

Published 30 December 2009. Record last updated 16 June 2026. We keep this page's data up to date.

What it does

What is CVE-2009-4484? In plain terms.

It can be attacked from anywhere on the internet without logging in. If it works, the attacker can read some data, change some data and slow it down.

The official 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 kind of flaw is it?

  • CWE-787Out-of-bounds Write
CVSS 2.0 scoreHigh · 7.5

How an attack on it works

Read straight from its severity rating, translated out of the shorthand.

  • Where an attacker can beAnywhere on the internet
  • How hard it is to pull offEasy: no special conditions
  • Login needed firstNo login needed
  • What an attacker getsCan read some data, change some data and slow it down

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

Exploitation

Is CVE-2009-4484 being exploited? Not that we know of.

It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 70%. That can change at any time, which is why we keep watching.

Known to be exploitedNoNot on the list of exploited flaws today
Chance of use in the next 30 days70%Its EPSS score, from the latest forecast

Timeline

  1. Published
  2. Record last updated
How Precursor Intelligence ranks it
57out of 100Medium

CVE-2009-4484 scores 57. Action: Plan remediation.

We keep the score of every published flaw up to date as the evidence changes. Four things go into the score, and evidence that criminals are actually using it counts most. In order:

  • Evidence it is being exploitedBiggest factor
  • How severe it isStrong factor
  • How widely exposed it isSmaller factor
  • Threat activity around itSmaller factor

85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score.

When CVE-2009-4484 matches software you track, it lands in your list with its score and the reasons behind it.

See your own ranked list →
Affected products

Who is affected by CVE-2009-4484? 5 products.

The published record lists 5 products from 5 vendors. Versions are shown as published: "5.0.0 to before 5.0.90" means from 5.0.0 up to, but not including, 5.0.90. If you run one of these, check your version, then go to the fix below.

Remediation

How do I fix CVE-2009-4484? Four steps.

  1. Check whether you run itCompare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list.
  2. Apply the vendor’s fixInstall the update named in the vendor’s advisory. We’ve put the advisories and patch notes first in the list.
  3. If you can’t patch todayFollow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
  4. Keep an eye on itTrack the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood.

References

36 links
Precursor Intelligence

Does CVE-2009-4484 affect you? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Start free →Book a demo

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

CVE-2009-4484 is a high-severity flaw in MySQL from Oracle, published on 30 December 2009. It can be attacked from anywhere on the internet without logging in. If it works, the attacker can read some data, change some data and slow it down.

It scores 7.5 out of 10 on the CVSS severity scale, which is high. Our risk score for CVE-2009-4484 is 57 out of 100, which is Medium. Its action is "Plan remediation". Not confirmed as exploited yet, but serious or likely enough that it should not wait for a quiet month.

It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 70%. That can change at any time, which is why we keep watching.

For MySQL from Oracle: 5.0.0 to before 5.0.90, 5.1.0 to before 5.1.43. The record lists 5 products in all, each with its versions, under "Who is affected" on this page.

Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet.

Keep exploring