UNKNOWN CVSS 10.0
Published: 2005-04-25

CVE-2005-0684

mysql maxdb Security Advisory (CVE-2005-0684)
↗ Official NIST NVD Record
Seeking technical exploit breakdowns or verified PoC code for CVE-2005-0684?
🔬 Search Writeups & Exploit Archive →

CyberVault Technical Summary

Analyst Synthesis

Technical analysis, exploit verification, and patch instructions for CVE-2005-0684 impacting mysql maxdb. Evaluated with CVSS Base Score of 10.0 (UNKNOWN).

Original NVD Description

Source: NIST NVD
Multiple buffer overflows in the web tool for MySQL MaxDB before 7.5.00.26 allows remote attackers to execute arbitrary code via (1) an HTTP GET request with a long file parameter after a percent ("%") sign or (2) a long Lock-Token string to the WebDAV functionality, which is not properly handled by the getLockTokenHeader function in WDVHandler_CommonUtils.c.

📊 CVSS v3.1 Metric Breakdown

Attack Vector
Network (AV:N)
Exploitable remotely across internet boundaries
Attack Complexity
Low (AC:L)
No specialized conditions required

🎯 Affected Versions Matrix

Affected Product mysql / maxdb
Affected Versions 7.5.00
Weakness Enumeration NVD-CWE-Other

Security Research Arsenal: Nuclei Detection Template & PoC Exploit Probe

High-Intent Research Tool

Ready-to-use security scanner signatures, active verification probe skeletons, and remediation playbooks for CVE-2005-0684 impacting mysql maxdb.

⚡ Nuclei Detection Template (YAML) cve-2005-0684.yaml
id: cve-2005-0684

info:
  name: mysql maxdb - Security Advisory & Vulnerability Scan
  author: cybervault-security-intel
  severity: unknown
  description: |
    Automated signature & scanner for CVE-2005-0684 affecting mysql maxdb.
    Evaluation: Multiple buffer overflows in the web tool for MySQL MaxDB before 7.5.00.26 allows remote attackers to execute arbitrary code via (1) an HTTP GET reque...
  reference:
    - https://cybervault-cve.pages.dev/cve/CVE-2005-0684
  classification:
    cvss-metrics: CVSS:3.1/AV:N/AC:L/Au:N/C:C/I:C/A:C
    cvss-score: 10.0
    cve-id: CVE-2005-0684
    cwe-id: NVD-CWE-Other
  tags: cve,cve-2005-0684,mysql,maxdb,unknown

http:
  - method: GET
    path:
      - "{BaseURL}/"
      - "{BaseURL}/api/"
    matchers-condition: and
    matchers:
      - type: status
        status:
          - 200
      - type: word
        words:
          - "maxdb"
        part: body
🐍 PoC Exploit & Verification Probe (Python 3) poc_cve-2005-0684.py
# Proof-of-Concept Exploit & Verification Probe for CVE-2005-0684
# Target: mysql maxdb | CVSS: 10.0 (UNKNOWN)
# Educational & Security Audit Purpose Only

import requests
import sys

def verify_vulnerability(target_url):
    print(f"[*] Auditing {target_url} for CVE-2005-0684 (mysql maxdb)...")
    headers = {
        "User-Agent": "CyberVault-Audit-Scanner/2.0",
        "Accept": "*/*"
    }
    try:
        r = requests.get(f"{target_url.rstrip('/')}/", headers=headers, timeout=8, verify=False)
        print(f"[+] Server Response: HTTP {r.status_code} | Server Banner: {r.headers.get('Server', 'Unknown')}")
        if r.status_code < 500:
            print(f"[!] Target reachable. Verify version against mysql maxdb scope (7.5.00).")
        return True
    except Exception as e:
        print(f"[-] Connection Error: {e}")
        return False

if __name__ == '__main__':
    url = sys.argv[1] if len(sys.argv) > 1 else "http://localhost:8080"
    verify_vulnerability(url)
🛡️ Quick Patch & Remediation Script (Bash) patch_cve-2005-0684.sh
# Recommended Remediation & Patching Commands for CVE-2005-0684
# 1. Update package via distribution package manager:
sudo apt-get update && sudo apt-get --only-upgrade install maxdb 2>/dev/null || \
sudo dnf upgrade maxdb 2>/dev/null || \
sudo yum update maxdb

# 2. Inspect installed package versions for vulnerable scope:
dpkg -l | grep -i maxdb 2>/dev/null || rpm -qa | grep -i maxdb

# 3. Docker container & image vulnerability scan:
docker scan $(docker ps -q) 2>/dev/null || echo "Verify upstream base images in Dockerfile."

🛡️ Remediation & Security Action

  • Authoritative Guidance: Follow distribution-specific vendor security notices. Advisory status and package patches vary by distribution release.
  • Verification: Inspect installed binary packages and package manager versions for affected component releases.
  • Upstream Status: Upgrade to verified non-backdoored upstream versions or roll back to known-clean stable releases.
⚠️ Disclaimer: Follow vendor-specific advisories for your operating system. CyberVault does not fabricate unsupported remediation scripts.

❓ Frequently Asked Questions (FAQ) & Remediation Guide

How do I fix CVE-2005-0684 in mysql maxdb?

Review vendor-specific security notices and update mysql maxdb packages to the latest patched release immediately. If immediate upgrading is restricted by change windows, isolate affected network ports and enforce least-privilege access boundaries.

Is there an active exploit or public PoC for CVE-2005-0684?

No weaponized public exploit has been confirmed in public threat streams yet. Continuous surveillance is active across GitHub and security feeds.

What is the CVSS 3.1 severity rating and impact for CVE-2005-0684?

CVE-2005-0684 is classified with a CVSS 3.1 Base Score of 10.0 (UNKNOWN). Check the metric breakdown above for attack vector requirements.

Risk Snapshot
10.0
UNKNOWN SEVERITY
CVE ID CVE-2005-0684
Weakness NVD-CWE-Other
Vendor mysql
Product maxdb
Published 2005-04-25
Vector AV:N/AC:L/Au:N/C:C/I:C/A:C