Skip to content
Fencer Vulns
medium 5.0

CVE-2006-1517 json

sql_parse.cc in MySQL 4.0.x up to 4.0.26, 4.1.x up to 4.1.18, and 5.0.x up to 5.0.20 allows remote attackers to obtain sensitive informatio…

published 2006-05-05 20 y ago modified 2026-06-16 4 mo ago also EUVD-2006-1521

cvss
5.0
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
5.1%
EPSS 5.1% chance of exploitation in 30 days, percentile 92%
public exploits
0
none known

Summary

sql_parse.cc in MySQL 4.0.x up to 4.0.26, 4.1.x up to 4.1.18, and 5.0.x up to 5.0.20 allows remote attackers to obtain sensitive information via a COM_TABLE_DUMP request with an incorrect packet length, which includes portions of memory in an error message.

Patch / fix

  • mysql RHEL 4 4.1.20-1.RHEL4.1
  • mysql-bench RHEL 4 4.1.20-1.RHEL4.1
  • mysql-server RHEL 4 4.1.20-1.RHEL4.1

red hat advisories RHSA-2006:0544

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2006-1517 updated

security flaw

  • Red Hat Enterprise Linux AS version 4 mysql 4.1.20-1.RHEL4.1, mysql-bench 4.1.20-1.RHEL4.1, mysql-server 4.1.20-1.RHEL4.1 Red Hat Enterprise Linux Desktop version 4 mysql 4.1.20-1.RHEL4.1, mysql-bench 4.1.20-1.RHEL4.1, mysql-server 4.1.20-1.RHEL4.1 Red Hat Enterprise Linux ES version 4 mysql 4.1.20-1.RHEL4.1, mysql-bench 4.1.20-1.RHEL4.1, mysql-server 4.1.20-1.RHEL4.1 Red Hat Enterprise Linux WS version 4 mysql 4.1.20-1.RHEL4.1, mysql-bench 4.1.20-1.RHEL4.1, mysql-server 4.1.20-1.RHEL4.1
    fixed: vendor fix RHSA-2006:0544

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

5.06% chance of exploitation in the next 30 days, higher than 92% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:P/I:N/A:N

Classification

Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.