Web crawl snapshots generously donated from Accelovation. This data is currently not publicly accessible.
From the site:
Accelovation is pioneering the delivery of Insight Discovery™ software solutions that help companies move from innovation idea to product reality faster and with more success.
Our solutions are used by leading firms in the Fortune 500 and beyond – companies from a diverse set of industries ranging from consumer packaged goods to high tech, foods to chemicals, and others. We help them mine the online world for market and technical insights to help speed the process of innovation.
This page lists security patches, in the form of Critical Patch Updates and Security Alerts, that Oracle
has released. The page is updated when new Critical Patch Updates and Security Alerts are released, and it is possible
to receive notification of releases by email.
Click here for instructions on how to configure email notifications. Click here to read the Technical White Paper, "Critical Patch Update Implementation Best Practices"
Critical Patch Updates
Starting 2005, Critical Patch Updates are the primary means of releasing security fixes for Oracle products.
They are released on the Tuesday closest to the 15th day of January, April, July and October. The next four dates are:
16 January 2007
17 April 2007
17 July 2007
16 October 2007
The Critical Patch Updates released to date are listed in the following table.
Before 2005, Security Alerts were the primary means of releasing security fixes for Oracle products.
Each Security Alert has a severity rating indicating the security risk of the vulnerabilities
within the alert. The Security Alerts released to date are listed in the following table.
Click here for definitions of the
Policy Statement on Information Provided in
Critical Patch Updates and Security Alerts
Oracle conducts an analysis of each security vulnerability
addressed by a Critical Patch Update (CPU) or a Security Alert. The
results of the security analysis are reflected in the severity of the
CPU or Security Alert and the associated documentation describing, for
example, the type of vulnerability, the conditions required to exploit
it and the result of a successful exploit. Oracle provides this
information, in part, so that customers may conduct their own risk
analysis based on the particulars of their product usage.
As a matter of policy, Oracle will not provide additional information
about the specifics of vulnerabilities beyond what is provided in the
CPU or Security Alert notification, the pre-installation notes, the
readme files, and FAQs. Oracle provides all customers with the same
information in order to protect all customers equally. Oracle will
not provide advance notification or "insider information" on CPU or
Security Alerts to individual customers. Finally, Oracle does not
develop or distribute active exploit code (or "proof of concept code")
for vulnerabilities in our products.
If you are an Oracle customer or an Oracle partner, please use
to submit a Service Request on any potential Oracle product security vulnerability.
Otherwise, please email
with your discovery. We encourage people who wish to contact Oracle Security to employ
email encryption, using our