CVE-2006-4305 in the critical feed json
Buffer overflow in SAP DB and MaxDB before 7.6.00.30 allows remote attackers to execute arbitrary code via a long database name when connec…
published 2006-08-30 20 y ago modified 2026-06-16 4 mo ago also EUVD-2006-4293
- cvss
- 10.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 71.7%
- EPSS 71.7% chance of exploitation in 30 days, percentile 99.4%
- public exploits
- 2
- Metasploit, Exploit-DB
Summary
Buffer overflow in SAP DB and MaxDB before 7.6.00.30 allows remote attackers to execute arbitrary code via a long database name when connecting via a WebDBM client.
Patch / fix
- securityfocus.com/bid/19660 patch
- debian.org/security/2006/dsa-1190 advisory
Timeline
- First public exploit (Metasploit exploit/windows/http/maxdb_webdbm_database)
- Published
Exploit prediction
71.75% chance of exploitation in the next 30 days, higher than 99.4% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- Metasploit exploit/windows/http/maxdb_webdbm_database MaxDB WebDBM Database Parameter Overflow metasploit exploit, good rank, 2006-08-29
- EDB-16765 MaxDB WebDBM - 'Database' Remote Overflow (Metasploit) remote, 2010-09-20
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 10.0 | AV:N/AC:L/Au:N/C:C/I:C/A:C |
References
-
debian.org
/security/2006/dsa-1190
vendor-advisory, patch
-
securityfocus.com
/bid/19660
vdb-entry, patch
-
symantec.com
/enterprise/research/SYMSA-2006-009.txt
vendor-advisory
-
secunia.com
/advisories/21677
third-party-advisory, vendor-advisory
-
secunia.com
/advisories/22518
third-party-advisory, vendor-advisory
-
securitytracker.com
/id?1016766
vdb-entry, vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/28636
vdb-entry
-
securityfocus.com
/archive/1/444601/100/0/threaded
mailing-list
- dev.mysql.com /doc/maxdb/changes/changes_7.6.00.32.html
-
vupen.com
/english/advisories/2006/3410
vdb-entry
Sources
- CVE List CVE-2006-4305
- NVD CVE-2006-4305
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.