bugtraq - Re: Bypassing Oracle dbms

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <06e001c6b200$39c8e890$ab817818@ngssoftware.com>
Date: Fri, 28 Jul 2006 05:42:24 +0100
From: "David Litchfield" <davidl@...software.com>
To: <ak@...-database-security.com>, <bugtraq@...urityfocus.com>
Subject: Re: Bypassing Oracle dbms_assert

> Today I released a new whitepaper "Bypassing Oracle dbms_assert".
<SNIP>
> Oracle has no problem with the release of this information
> ("Oracle sees no problem with your publication of the
> white paper.")

The reason Oracle sees no problem with the release of the paper is that for 
your technique to work the DBMS_ASSERT.QUALIFIED_SQL_NAME has to be used in 
the wrong context; you simply wouldn't use QUALIFIED_SQL_NAME in this 
manner - i.e. within quotes. I've just had a quick look through the SYS 
packages and find no instance of DBMS_ASSERT.QUALIFIED_SQL_NAME being used 
this way. If there is such a case, in other words I've missed it, then it 
would be a flaw in the package/procedure/function itslef and not a problem 
with DBMS_ASSERT - with the fix being to use the correct DBMS_ASSERT 
function instead of QUALIFIED_SQL_NAME or alternatively use a bind variable.

Cheers,
David