Call: +44 (0)7759 277220 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 has released CPU April 18th 2006"] [Next entry: "Alex has released an advisory for his bug in CPU April 2006"]

What is amazing is that a lot of CPU patches are not available until May!!

Alex just pointed out to me that when you go to download the April CPU 2006 patches there is a note that tells you that the patches are not available for a lot of platforms until May 1st (many versions and platforms) and for some platforms the ETA is 15th May (e.g - on Solaris for x86). I also notice that is available for Unix, Linux and Windows but is not. I thought the policy was to fix the later verisons first?

I think it is bad form that Oracle release an advisory telling customers to patch their databases but for many customers they will have to wait around 13 days and some almost one further month for the patches to be available. I remember that the January CPU had many more fixes but I don't remember that as many platforms had delayed patch releases.

It is not really a quarterly patch schedule if the patches are not available quarterly for some customers. I think Oracle should have delayed the release of the advisory as roughly 50% of the patches / platforms listed have delayed ETA's. It is hard to comment further without detailed knowledge of how many customers are on each platform / version.