[9592] in bugtraq

home help back first fref pref prev next nref lref last post

Re: KSR[T] Advisory #10: mSQL ServerStats

daemon@ATHENA.MIT.EDU (John W. Temples)
Mon Feb 15 16:24:24 1999

Date: 	Mon, 15 Feb 1999 13:10:44 -0800
Reply-To: "John W. Temples" <john@KUWAIT.NET>
From: "John W. Temples" <john@KUWAIT.NET>
X-To:         "Dave G." <dhg@KSRT.ORG>
To: BUGTRAQ@NETSPACE.ORG
In-Reply-To:  <Pine.SUN.3.96.990215045256.4961A-100000@sitio>

On Mon, 15 Feb 1999, Dave G. wrote:

> Compromise:          If host based access control is disabled, a
>                      remote attacker can use the user names listed in
>                      the connection table to access databases.  If host
>                      based access control is enabled, a remote attacker
>                      could launch a more complex attack (like DNS cache
>                      poisoning) to access mSQL databases.

This is hardly news; mSQL's access control is extremely weak.
ServerStats probably makes it easier to get into an mSQL database, but
if remote access is enabled, you simply need to know an authorized
username (say, "root") to log into the database -- there are no
passwords.  And you don't even need a username to perform DoS attacks,
since mSQL is a single-threaded server -- just telnet to mSQL's port
and sit there.  As far as I can see, the only thing that's changed
since I posted about this in September, 1997, is that remote access is
now disabled by default.

--
John W. Temples, III       ||       Providing the first public access Internet
Gulfnet Kuwait             ||            site in the Arabian Gulf region

home help back first fref pref prev next nref lref last post