Auditing an Oracle database for security issues is very important. PeteFinnigan.com provides all of the information and tools that you will need Click here for details of PeteFinnigan.com Limited's detailed Oracle database security audit service Click here for details of PeteFinnigan.com Limited's Oracle Security Training Courses
There are 75 visitors online    
Cookie Policy:We only use essential cookies on small sections of this website. For details see here.

Pete Finnigan's Oracle security weblog


Home » Archives » July 2005 » Oracle have issued a second email with another exploitable vulnerability in 10.1.0.2 in CPU 12APR

[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 10.1.0.2 in CPU 12APR

July 7th, 2005 by Pete


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 10.1.0.2 (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 10.1.0.2. 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:


SQL>@?\ctx\admin\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.

July 2005
SMTWTFS
     12
3456789
10111213141516
17181920212223
24252627282930
31      

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.

Weblog Home
Weblog Archives


Home
Oracle Security Tools page
Oracle security papers
Oracle Security alerts

Web Development
SQL Server Security

RSS 1.0 FEED
RSS 2.0 FEED
Atom 0.3 FEED
Powered by gm-rss 2.0.0


Valid XHTML 1.0!