dbcve.org
MsqlApplication · Hughes

CVE-2000-0012

HIGH · 10.0 CVSS v2.0 Published 1999-12-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
Buffer overflow in w3-msql CGI program in miniSQL package allows remote attackers to execute commands.

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

Buffer overflow vulnerability in the w3-msql CGI program from the miniSQL (mSQL) package allows remote attackers to execute arbitrary commands via crafted input to the CGI.

MitigationRemove or disable the vulnerable w3-msql CGI program immediately; if the CGI is required, migrate to a supported database solution and remove the legacy mSQL installation.

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
MsqlApplication
Affected:= 2.0.11

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. Locate the w3-msql CGI program
    Search common CGI directories (such as /cgi-bin/, /usr/lib/cgi-bin/, /var/www/cgi-bin/) for a file named 'w3-msql' or 'w3-msql.exe'. Also check the mSQL installation directory for this CGI.
    Affected if The w3-msql CGI file exists on the system
  2. Identify the installed mSQL version
    Check the mSQL version by running 'msql -V' or 'msql -version' from the command line. Alternatively, examine the mSQL installation files or package metadata for version information.
    Affected if The installed mSQL version is exactly 2.0.11
  3. Verify the CGI is accessible via web server
    Inspect the web server configuration (e.g., Apache httpd.conf, nginx config) to confirm that the w3-msql CGI is enabled and mapped to a URL path accessible from the web.
    Affected if The w3-msql CGI is configured and accessible through the web server
  4. Confirm the CGI is executable
    Check file permissions on the w3-msql CGI file to ensure it has execute permissions (typically chmod 755) and can be invoked by the web server user.
    Affected if The CGI file has execute permissions and can be run by the web server process

The environment is affected if the w3-msql CGI is present and the installed mSQL version is exactly 2.0.11, as this specific version contains the vulnerable CGI program.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Remove or disable the vulnerable w3-msql CGI program immediately; if the CGI is required, migrate to a supported database solution and remove the legacy mSQL installation.

Fix this in Msql Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,730
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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