Features 
Thanks to ODAT, you can:

• search valid SID on a remote Oracle Database listener via:
  • a dictionary attack
  • a brute force attack
  • ALIAS of the listener
• search Oracle accounts using:
  • a dictionary attack
  • each Oracle user like the password (need an account before to use this attack)
• execute system commands on the database server using:
  • DBMS_SCHEDULER
  • JAVA
  • external tables
  • oradbg
• download files stored on the database server using:
  • UTL_FILE
  • external tables
  • CTXSYS
• upload files on the database server using:
  • UTL_FILE
  • DBMS_XSLPROCESSOR
  • DBMS_ADVISOR
• delete files using:
  • UTL_FILE
• send/reveive HTTP requests from the database server using:
  • UTL_HTTP
  • HttpUriType
• scan ports of the local server or a remote server using:
  • UTL_HTTP
  • HttpUriType
  • UTL_TCP
• exploit the CVE-2012-313 (http://cvedetails.com/cve/2012-3137)
• pickup the session key and salt for arbitrary users
• attack by dictionary on sessions

RedoWalker is a tool to explore Oracle database transaction logs, otherwise known as redo logs. Any time changes are made to the database server, for example after an INSERT, DELETE or UPDATE, they are recorded in the redo log.

These redo logs are stored in a proprietary and undocumented format and, as such, are unreadable and unintelligible without a tool that can decipher them. Oracle does provide a tool called LogMiner to access the redo logs but to use it access to a live database server is required. RedoWalker is a replacement for LogMiner and removes this requirement. This is particularly useful for auditors, forensic examiners and breach investigators. DBAs can also take advantage of RedoWalker for troubleshooting and problem isolation without the database server; using LogMiner could cause the database server to slow down.

RedoWalker dumps Oracle redo logs to an XML format; it specifically dumps redo entries fro DDL, INSERTs, UPDATEs, DELETEs and associated UNDO records.