Date: Thu, 7 Jan 1999 11:19:49 -0800 (PST) From: Jason Ackley <jason@ackley.net> To: lwn@lwn.net Subject: Re: Oracle8 TNSLSNR DoS Hiya, just noticed the tidbit on myself regarding the Oracle8 DoS with TNSLSNR, here is some more affected versions if you are interested in posting them: --- From: bruce_redmon@sra.com I tested this on Sequent Dynix and sure enough it runs the process out of control. If it happens on this platform I suspect this can happen on any platform. --- From: bcf@jwfc.acom.mil confirmed on Oracle 8.0.3 on Solaris 2.6 port 1521 confirmed on Oracle 8.0.5 on Solaris 2.6 port 1526 --- From: giblin <giblin@fibre.com> Hello, I gave it a try on a Solaris 2.6 ( heavily patched ) and Oracle 8.0.4 Database CPU utilization climbed and hovered at a high 49.9x% and didn't fall below 49.7x%. This is on a UE450 with 2 processors and 1.5GB RAM. Oracle required a restart to get it back into previous working condition. Hmmm... Nice :) --- From: Adam vonNieda <adam@vonnieda.org> I've tried the bug on my Linux box, (8.0.5), and it pegged instantly. I then tried it on one of my IBM SP (8 way) nodes running AIX 4.3 and Oracle 8.0.4.2.1, and essentially lost the processor that the listener is attached to instantly. So, it won't totally dog an SMP machine, but I wouldn't expect much response from the listener! Thanks for the info. --- From: gabriel magee <gmagee@nmia.com> I just tried it on NT SP3 (+hotfixes) Oracle 8.0.5.0.0 Production on a PII/350 with the same results. 100% CPU until you kill the listener. Could maybe choose a different protocol adapter in the meantime, too... --- Many thanks to everyone that sent in reports! We still seem to be missing information for SGI/IRIX, any takers? cheers, -- Jason Ackley jason@ackley.net