DDLDUMP Log Analysis v0.1 beta
DDLDUMP parses an Oracle redo log (transaction file) and dumps all DDL statements, such as GRANT, CREATE, ALTER, DROP, REVOKE, etc, in XML.
C:\app\david\oradata\orcl11g>ddldump REDO01.log ddl
<?xml version=”1.0″?>
<LOG>
<FILENAME>REDO01.log</FILENAME>
<database_sid>ORCL11G</database_sid>
<version>11.1</version>
<ltimestamp>01/02/2010 15:26:02</ltimestamp>
<blocksize>512</blocksize>
<nab>234</nab>
<lowscn>3977649</lowscn>
<nextscn>3977776</nextscn>
<ENTRIES>
<ENTRY>
<TIMESTAMP>04/03/2010 01:16:34</TIMESTAMP>
<RDRCOFST>0x0001CB2C</RDRCOFST>
<CHVCOFST>0x0001CB5C</CHVCOFST>
<SESSION_USER>SYS</SESSION_USER>
<CURRENT_USER>SYS</CURRENT_USER>
<SQL_STATETMENT>create user hax0r identified by VALUES ‘9A3502887F7210C4’ </SQL_STATETMENT>
<SCHEMA>hax0r</SCHEMA>
<OBJECT></OBJECT>
</ENTRY>
</ENTRIES>
</LOG>
C:\>
RDRCOFST is the hexadecimal offset into the redolog file where the redo entry containing the DDL statement can be found CHVCOFST is the hexadecimal offset into the redolog file where the change vector containing the DDL statement can be found TIMESTAMP is the time and date when the redo entry was written to the log file. SESSION_USER is the user that is logged on and initiated the DDL statement CURRENT_USER is the user under whose authority the DDL actually executes. If session_user and current_user are different it could be indicitive of a SQL injection attack. SQL_STATEMENT is the DDL that was executed.
SCHEMA, if present, is the schema upon which the DDL acts.
OBJECT, if present, is the object upon which the DDL acts.
About the Author
NJ Ouchn "Passion is needed for any great work, and for the revolution, passion and audacity are required in big doses"
Related Posts
LIEF v0.7.0 – Library to Instrument Executable Formats →
Invtero.net – Forensics, Memory Integrity & Assurance Tool →
TCHunt-ng v1.2 – Reveal encrypted files →
