Call: +44 (0)1904 557620 Call

Pete Finnigan's Oracle Security Weblog

This is the weblog for Pete Finnigan. Pete works in the area of Oracle security and he specialises in auditing Oracle databases for security issues. This weblog is aimed squarely at those interested in the security of their Oracle databases.

[Previous entry: "Oracle have issued an email alert that CPU April 2005 is vulnerable to exploit"] [Next entry: "David Litchfield has released an advisory for the recent CPU 12 April vulnerabilities"]

Oracle have issued a second email with another exploitable vulnerability in in CPU 12APR

What a day for Oracle, two security issues have been found in their Critical Patch Update April 12. This does not look good for their Q&A departments after all the good work making better information available with released patches.

This second email has been sent to customers who have downloaded the patch for CPU 12 April for the Oracle database (Patch 4181849 or 4213305) for Windows 32-bit and 64-bit platforms.

It goes on to say that an installation script was missing causing the context component to not be patched correctly. If Context is not installed there is not an issue and it is only a problem for Windows platforms and version If Context was installed I will repeat the suggested instructions here:-

1. Backup of the file driload.pkh from %ORACLE_HOME%\ctx\admin.
2. Copy the file driload.pkh from "%ORACLE_HOME%\rdbms\admin" to "%ORACLE_HOME%\ctx\admin":

>cp %ORACLE_HOME%\ctx\admin\driload.pkh %ORACLE_HOME%\ctx\admin\driload.pkh.back
>cp %ORACLE_HOME%\rdbms\admin\driload.pkh %ORACLE_HOME%\ctx\admin\driload.pkh

3. Startup all the database instances running out of the ORACLE_HOME being patched.
4. For each database instance running out of the ORACLE_HOME being patched, connect to the database using Sqlplus as sysdba and run driload.pkh:


Again Oracle expresses their apologies for this unfortunate issue. If you are familiar with the bugs discovered and fixed in CPU 12 April you will immediately recognise that itís possible to escalate privileges to a DBA with this package on Windows even if CPU 12 Apr has been installed so it is important to follow these instructions to secure the problem.