bugtraq - Re: Workaround for unpatched Oracle PLSQL Gateway flaw

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <002b01c62ce8$a4a3a260$2200a8c0@ngssoftware.com>
Date: Wed, 8 Feb 2006 19:48:32 -0000
From: "David Litchfield" <davidl@...software.com>
To: <bugtraq@...urityfocus.com>
Subject: Re: Workaround for unpatched Oracle PLSQL Gateway flaw

> So, like, what about 
> http://www.integrigy.com/info/IntegrigySecurityAnalysis-MODPLSQLVuln.pdf

This provides an excellent analysis of the problem. Further, it discusses 
the recommendation made by Vladimir Zakharychev from Webrecruiter. This 
recommendation is to set the "always_describe" / 
"PlsqlAlwaysDescribeProcedure" to "yes" / "on" in the "wdbsvr.app" / 
"dads.conf" file. This is a simple workaround and, as I can confirm, it does 
prevent exploitation. Why on earth didn't Oracle make this simple 
recommendation in the January 2006 CPU?

I hereby withdraw my workaround and would encourage everyone to adopt 
Vladimir's.

Cheers,
David Litchfield