Re: @(#) Mordred Labs advisory 0x0001: Buffer overflow in

From: Jan Wieck <JanWieck(at)Yahoo(dot)com>
To: Dann Corbit <DCorbit(at)connx(dot)com>
Cc: Neil Conway <neilc(at)samurai(dot)com>, Mark Pritchard <mark(at)tangent(dot)net(dot)au>, Justin Clift <justin(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: @(#) Mordred Labs advisory 0x0001: Buffer overflow in
Date: 2002-08-20 13:53:47
Message-ID: 3D6249EB.F92933EF@Yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Dann Corbit wrote:
> [...]
>
> What I am saying is that there is nothing that could possibly be more
> important than fixing this, except some other known problem that could
> also cause billions of dollars worth of damage. Are there any such
> problems besides the buffer overrun problems?

And what others tried to tell you is, that there are different types of
systems and levels of vulnerability. A software that by nature needs to
be exposed to the internet (like an SMTP, HTTP or SSH server) is in high
danger and needs to be fixed immediately. But software that by nature
needs to be well protected from uncontrolled access (like a database, a
backup management system or a logical volume manager) does not.

The matter of the fact is, that if you grant someone access to your
database that gives him the power to execute the statement that triggers
this bug, you're lost anyway. Whatever constraints you have set up, an
empty database is usually very consistent but not neccessarily useful.

Jan

--

#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck(at)Yahoo(dot)com #

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Copeland 2002-08-20 14:05:16 Re: @(#) Mordred Labs advisory 0x0001: Buffer overflow in
Previous Message Greg Copeland 2002-08-20 13:48:00 Re: @(#) Mordred Labs advisory 0x0001: Buffer overflow in