Re: Connection hijacking in SQL Server 2000
From: Bernd Eckenfels (ecki-news2002-06@lina.inka.de)Date: 06/28/02
- Next message: Jason: "ATM Security"
- Previous message: Dieter Henss: "User two factor authentication on laptops"
- In reply to: Wes Gamble: "Connection hijacking in SQL Server 2000"
- Next in thread: BP Margolin: "Re: Connection hijacking in SQL Server 2000"
- Reply: BP Margolin: "Re: Connection hijacking in SQL Server 2000"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: Bernd Eckenfels <ecki-news2002-06@lina.inka.de> Date: 28 Jun 2002 02:00:49 GMT
In comp.security.misc Wes Gamble <w.gamble@pentasafe.com> wrote:
I would assume that an exploiter would have to know the
> protocol used by SQL Server so that they could construct reasonable
> looking packets to send to SQL Server.
The TDS Protocol is open so this is not an issue. Highjacking those
connections would involve eighter spoofing on TCP connections, which require
physical access to the network and is hard to achieve if encryption is
turned on, or you modify the connection pool. I am not sure how much work
that is, but i simply *asume* you have to be local admin on the machine.
The simplest protection is not to allow untrusted access to your network or
clients.
Greetings
Bernd
- Next message: Jason: "ATM Security"
- Previous message: Dieter Henss: "User two factor authentication on laptops"
- In reply to: Wes Gamble: "Connection hijacking in SQL Server 2000"
- Next in thread: BP Margolin: "Re: Connection hijacking in SQL Server 2000"
- Reply: BP Margolin: "Re: Connection hijacking in SQL Server 2000"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|