How severe is CVE-2005-1274?

CVE-2005-1274 has a CVSS 2.0 base score of 10.0, rated critical severity.

Is CVE-2005-1274 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 4% (90th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2005-1274?

CVE-2005-1274 primarily affects Mysql Maxdb. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2005-1274?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

When was CVE-2005-1274 published?

CVE-2005-1274 was published on 2005-04-26 and last updated on 2026-06-16.

CVE-2005-1274

CVE-2005-1274 is a critical-severity vulnerability in Mysql Maxdb with a CVSS 2.0 base score of 10.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Critical (CVSS 2.0 base score 10.0)
EPSS exploit prediction: 4% (90th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Mysql Maxdb
Published: 2005-04-26
Last modified: 2026-06-16

Description

Stack-based buffer overflow in the getIfHeader function in the WebDAV functionality in MySQL MaxDB before 7.5.00.26 allows remote attackers to execute arbitrary code via an HTTP unlock request and a long "If" parameter.

Frequently asked questions

What is CVE-2005-1274?: Stack-based buffer overflow in the getIfHeader function in the WebDAV functionality in MySQL MaxDB before 7.5.00.26 allows remote attackers to execute arbitrary code via an HTTP unlock request and a long "If" parameter.
How severe is CVE-2005-1274?: CVE-2005-1274 has a CVSS 2.0 base score of 10.0, rated critical severity.
Is CVE-2005-1274 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 4% (90th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2005-1274?: CVE-2005-1274 primarily affects Mysql Maxdb. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2005-1274?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2005-1274 published?: CVE-2005-1274 was published on 2005-04-26 and last updated on 2026-06-16.

References

http://www.idefense.com/application/poi/display?id=236&type=vulnerabilities

Affected products (2)

cpe:2.3:a:mysql:maxdb:*:*:*:*:*:*:*:*
cpe:2.3:a:mysql:maxdb:7.5.00.25:*:*:*:*:*:*:*

More vulnerabilities in Mysql Maxdb

CVE-2006-4305 — Critical (CVSS 10.0): Buffer overflow in SAP DB and MaxDB before 7.6.00.30 allows remote attackers to execute arbitrary code via a long…
CVE-2005-0684 — Critical (CVSS 10.0): Multiple buffer overflows in the web tool for MySQL MaxDB before 7.5.00.26 allows remote attackers to execute arbitrary…
CVE-2004-1168 — Critical (CVSS 10.0): Stack-based buffer overflow in the WebDav handler in MaxDB WebTools 7.5.00.18 and earlier allows remote attackers to…
CVE-2005-0111 — High (CVSS 7.5): Stack-based buffer overflow in the websql CGI program in MySQL MaxDB 7.5.00 allows remote attackers to execute…
CVE-2005-0083 — Medium (CVSS 5.0): MySQL MaxDB 7.5.00 for Windows, and possibly earlier versions and other platforms, allows remote attackers to cause a…
CVE-2005-0082 — Medium (CVSS 5.0): The sapdbwa_GetUserData function in MySQL MaxDB 7.5.0.0, and other versions before 7.5.0.21, allows remote attackers to…

All CVEs affecting Mysql Maxdb →