dbcve.org
MaxdbApplication · MySQL

CVE-2005-1274

HIGH · 10.0 CVSS v2.0 Published 2005-04-26
Fix available
A fix is available. Upgrade to after 7.5.00.23 or later.
See remediation →
100/100
Remediation priority · Urgent
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
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.

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 · high confidence

Stack-based buffer overflow in the getIfHeader function within MySQL MaxDB's WebDAV implementation allows remote attackers to execute arbitrary code by sending an HTTP unlock request with an oversized 'If' parameter, enabling complete system compromise.

MitigationUpgrade MySQL MaxDB to version 7.5.00.26 or later to patch the vulnerability. If immediate patching is not possible, disable WebDAV functionality or restrict network access to the HTTP listener.

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
MaxdbApplication
Affected:<= 7.5.00.23= 7.5.00.25

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
Complete
Integrity
Complete
Availability
Complete

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

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. Verify MySQL MaxDB installation
    Check for MySQL MaxDB installation directories (e.g., C:\maxdb or /opt/sap/maxdb) or search for 'maxdb' processes running on the system.
    Affected if MySQL MaxDB is not installed on the system.
  2. Determine installed MaxDB version
    Run the MaxDB version command (e.g., 'sqlcli -v' or check version info in the MaxDB database manager), or inspect version files in the installation directory.
    Affected if The installed version is 7.5.00.23 or lower, or the installed version is exactly 7.5.00.25.
  3. Confirm WebDAV is enabled
    Check MaxDB configuration for WebDAV settings. Look for WebDAV-related configuration files or check the MaxDB Database Manager for WebDAV status.
    Affected if WebDAV functionality is enabled in the MaxDB configuration.
  4. Verify HTTP listener is accessible
    Check if the MaxDB HTTP server is running and listening on its configured port (typically 9999). Use 'netstat' or similar tools to identify listening ports.
    Affected if The MaxDB HTTP listener is accessible over the network (not bound to localhost only or firewalled).

The system is affected only if MySQL MaxDB version 7.5.00.23 or lower, or exactly 7.5.00.25, is installed WITH WebDAV enabled AND the HTTP listener is network-accessible.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 7.5.00.23
Interim mitigation

Upgrade MySQL MaxDB to version 7.5.00.26 or later to patch the vulnerability. If immediate patching is not possible, disable WebDAV functionality or restrict network access to the HTTP listener.

Recommended fix High confidence

MaxDB 7.5.00.26 or later

  1. 1. Back up all MaxDB databases and configuration files before proceeding with any upgrade
  2. 2. Stop the MaxDB database service to prevent data corruption during upgrade
  3. 3. Download MaxDB version 7.5.00.26 or a later stable release from the official MySQL/SAP support portal
  4. 4. Install the upgraded MaxDB version following the standard upgrade procedures for your platform
  5. 5. After installation, verify that the WebDAV component has been updated to the fixed version
  6. 6. Start the MaxDB database service and verify normal operation
  7. 7. Test the WebDAV functionality to confirm the vulnerability is resolved
  8. 8. Monitor logs for any unusual activity related to the If header in WebDAV requests
Caveat Review release notes for any configuration or compatibility changes between your current version and 7.5.00.26 before upgrading; test in a non-production environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Maxdb Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2005-1274 — 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-2005-1274 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