CVE-1999-1260
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 · uneditedmSQL (Mini SQL) 2.0.6 allows remote attackers to obtain sensitive server information such as logged users, database names, and server version via the ServerStats query.
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 confidencemSQL 2.0.6 contains a vulnerability where the ServerStats query can be sent remotely without authentication, exposing sensitive server information including currently logged users, database names, and the server version. This information disclosure is exploitable over the network and can aid attackers in reconnaissance and planning further attacks.
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<= 2.0.6CVSS 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
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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 checksWork through these to decide whether this CVE applies to you.
-
Identify if mSQL is installedCheck for mSQL binaries and processes: look for 'msql' or 'miniSQL' in running processes (ps aux | grep -i msql), check for mSQL installation directories (/usr/local/Hughes, /usr/local/msql, /opt/msql), or check for the msql service running on common ports 1114 or 4334Affected if mSQL process or installation directory is found on the system
-
Determine the installed mSQL versionRun 'msql -V' or check the version file typically found in the mSQL installation directory (e.g., version file in /usr/local/Hughes/msql), or query the server directly if you have local accessAffected if Version is 2.0.6 or lower, or any version that cannot be determined but appears to be from the 2.x line
-
Check if mSQL service is network accessibleUse 'netstat -anp | grep -E "(1114|4334)"' or 'ss -tlnp | grep -E "(1114|4334)"' to check if mSQL ports are listening, then verify if those ports are exposed externally (nmap -p 1114,4334 <your-ip> from an external host or check firewall rules with 'iptables -L' or 'firewall-cmd --list-all')Affected if mSQL ports (1114, 4334) are listening and accessible from network addresses other than localhost
-
Verify if unauthenticated ServerStats query returns informationIf mSQL is network-accessible and you have permission, attempt a benign query using: echo -e "\x00\x00\x00\x01" | nc -nv <target-ip> 1114 or 4334, or use an msql client with no credentials to see if server statistics are returnedAffected if ServerStats query returns server version, logged users, database names, or other sensitive system information without requiring authentication
You are affected if mSQL version 2.0.6 or lower is installed and the service port is accessible from the network, allowing unauthenticated attackers to retrieve server statistics.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade to a patched version of mSQL if available. If no patch exists, restrict network access to the mSQL service port using firewall rules or network segmentation, or migrate to a supported database solution.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-1999-1260 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-1999-1260 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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