full-disclosure - Oracle Database 10g Rel. 2 - Event 10053 logs TDE wallet password in cleartext

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date: Tue Jan 17 20:54:10 2006
From: ak at red-database-security.com (Kornbrust, Alexander)
Subject: Oracle Database 10g Rel. 2 - Event 10053 logs TDE
	wallet password in cleartext

Hello FD-Reader

Event 10053 logs the TDE masterkey in cleartext into the trace file.
Oracle fixed this problem with CPU January 2006.

http://www.red-database-security.com/advisory/oracle_tde_wallet_password
.html

########################################################################
#

Name        Event 10053 logs TDE wallet password in cleartext 
Systems     Oracle Database 10g Release 2 
Severity    High Risk 
Category    Information disclosure 
Vendor URL  http://www.oracle.com/ 
Author      Alexander Kornbrust (ak at red-database-security.com)
Date        17 January 2005 (V 1.00)
Oracle Bug  5802023
Time to fix 190 days


Details:
########
The event 10053 is storing the masterkey of Oracle Transparent Data
Encryption unencrypted in a trace-file. A skilled attacker or
non-security DBA could set this special event to get the plaintext
masterkey for the TDE encryption. 

Test case:
##########
SQL> alter session set events='10053 trace name context forever, level
1';

Session altered.


SQL> ALTER SYSTEM SET WALLET OPEN IDENTIFIED BY "secretpassword";

System altered.
######### Test case ######



######### Excerpt from trace file ############ 
[] Current SQL statement for this session:
ALTER SYSTEM SET WALLET OPEN IDENTIFIED BY "secretpassword"
[]
######### Excerpt from trace file ############


Patch Information:
##################
Oracle fixed this issue with the patches from the critical patch update
january 2006 for Oracle 10g Release 2.

History:
########
11-jul-2005 Oracle secalert was informed
12-jul-2005 Bug confirmed
17-jan-2006 Oracle published the Critical Patch Update January 2006
(CPU January 2006)
17-jan-2006 Red-Database-Security published this advisory


(c) 2006 by Red-Database-Security GmbH
http://www.red-database-security.com