PDA

Bekijk Volledige Versie : Workaround for unpatched Oracle PLSQL Gateway flaw



David Litchfield
25/01/06, 19:45
There's a critical flaw in the Oracle PLSQL Gateway, a component of iAS, OAS
and the Oracle HTTP Server, that allows attackers to bypass the
PLSQLExclusion list and gain access to "excluded" packages and procedures.
This can be exploited by an attacker to gain full DBA control of the backend
database server through the web server.

This flaw was reported to Oracle on the 26th of October 2005. On November
the 7th NGS alerted NISCC (http://www.niscc.gov.uk) to the problem. It was
hoped that due to the severity of the problem that Oracle would release a
fix or a workaround for this in the January 2006 Critical Patch Update. They
failed to do so.

The workaround is trivial; using mod_rewrite, which is compiled into
Oracle's Apache distribution it is possible to stop the attack. The
workaround checks a user's web request for the presence of a right facing
bracket, ')'.

Add the following four lines to your http.conf file then stop and restart
the web server

RewriteEngine on
RewriteCond %{QUERY_STRING} ^.*\).*|.*%29.*$
RewriteRule ^.*$ http://127.0.0.1/denied.htm?attempted-attack
RewriteRule ^.*\).*|.*%29.*$ http://127.0.0.1/denied.htm?attempted-attack

I don't think leaving their customers vulnerable for another 3 months (or
perhaps even longer) until the next CPU is reasonable especially when this
bug is so easy to fix and easy to workaround. Again, I urge all Oracle
customers to get on the 'phone to Oracle and demand the respect you paid
for.

Cheers,
David Litchfield

x@x.com
01/02/06, 19:00
just a note that this rewrite rule causes things in htmldb not to work anymore...

ad@heapoverflow.com
04/02/06, 20:45
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

http://www.infoworld.com/article/06/01/27/74869_HNoraclefiresback_1.html

x@x.com wrote:
> just a note that this rewrite rule causes things in htmldb not to
> work anymore...
>
>
>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)

iQIVAwUBQ+FAP6+LRXunxpxfAQKOvBAAnS6b08sTCWVejnaO39 wbX/JkIVYphilt
CP7/CRO0DdTPWXp1jKkbKb+ILP/9zG0IbMtCVAa/73Us5DGuT7AgRp8aIlYk70Fo
idIpFYKBjYEuSyHFvLvmK025uo1B/b8XXS7sdFPtb8K1uiAuFxo6mOFvuPJLzC9X
/WPn4WOP+N1QTjIJT5WK3uRKBhlMoXE46oD1aGyfMecN9GZiwYQ kVClDsUUGr+8y
Z9j7f3AvMyVf70S4IqyRbuhxbwMWmCYvWayfa7hHwhKlaH6nCz MNk71fTtVxMo0k
HoisRn8HK6WIaGH2rv/MorYh/NWqMtKCV9HFk8TibtLtgg+yEHQmGh9qBmf7eEaK
lk/5h37orRkIg2a9qclDfzHp87o00NCFtWGm+nFmoi+P613YVaAlS UEDhWJkkzOV
4u+AE2roCUzGyvVOY1RUPHv8uBpUKBg2gArr7XVT3J9HG3wZCU 2qBHeqNDwHayCc
T2lf0Myw51jzyv6HCiq/2kbxTOnfcwJ+a+MDgzC3y9jJKH4Q3DOILbNN3oXG+0YS
QOghAVfixeGHeHw9loC2KcMzFOoJVt3c/MSJoolu7fVF/KMFT08Tw3jvbBJX3O56
c/IRanyA+ti7hl4LWm8sgTOVGd/nx8vSASdRi/vI7IqmLkebmrTjJwgdEEWvXShh
A3g41uHkecw=
=1Biz
-----END PGP SIGNATURE-----

a@b.com
08/02/06, 19:30
So, like, what about http://www.integrigy.com/info/IntegrigySecurityAnalysis-MODPLSQLVuln.pdf

David Litchfield
08/02/06, 21:30
> 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