According to Oracle, the workaround I posted, that prevents exploitation of
a critical vulnerability that Oracle has so far failed to fix, breaks
certain applications that sits atop their PLSQL Gateway. Though my
workaround prevents exploitation of the critical flaw and thus protects
vulnerable systems against attack, Oracle has made no effort to furnish me,
or anyone else for that matter, with more information on how the workaround
breaks some of their applications. As such, improving the workaround so it
doesn't break these few applications has been mildy annoying. But I think
I've tracked it down. The workaround as is
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
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
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
# Thanks, Mike Pomraning!
Cheers, David Litchfield