After 2 years advancing his career (and his family), Chris Gates is back with a new article. He'll be bringing you some Oracle hotness.
Thanks Chris, and it's great to have you back.
Permanent link: [Article]-Oracle Web Hacking Part I
By Chris Gates, CISSP, GCIH, C|EH, CPTS
Oracle applications are not what youíd call simple. I think any DBA or Oracle Application Server Administrator will be the first to attest to that fact. Oracle, with its great products, comes with some un-pleasantries. These are:
1. Oracle applications are complicated (hopefully we all agree on this).
2. They come with loads of default content and no clear way to remove that content. There is no IISLockdown equivalent for Oracle applications. Content you donít want must be removed manually. Some of this content can be used to run database queries, read documents, gather information via information leakage on the pages or perform XSS attacks.
3. Users have to pay for patches and extended advisory information (even then, no Proof of Concept code is released by Oracle).
4. And lastly, you have a fairly complicated patch/upgrade process which leads to an "itís working, donít touch it" mentality by a fair amount of admins.
This provides a target rich environment for pentesters and bad guys. Letís take a look.
Let us know what you think,