Nearly 50 vulnerabilities were fixed with Oracle Corp.'s latest quarterly volley of patches yesterday, but experts...
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
say that many critical issues haven't been addressed at all. Another concern: At least one fix issued last quarter failed to correct the issue it claimed to solve.
"Where are the large numbers of fixes expected?" asked Pete Finnigan, an Oracle expert and author of Oracle Security Step By Step -- A survival guide for Oracle security. "Alex Kornbrust and Esteban Martinez Fayo have big lists of bugs, some reported over 18 months ago,
"I hope Oracle has tested the patch sets better this time," Finnigan added. "A repeat of the recent set of vulnerabilities in the April Critical Patch Update [CPU] would not be good for Oracle's publicity."
According to David Litchfield, managing director at U.K.-based Next Generation Security Software Ltd., one set of vulnerabilities "fixed" by the April CPU -- a group of SQL injection bugs in DBMS_SUBSCRIBE and DBMS_ISUBSCRIBE -- was actually left unfixed. "On digging deeper you find that the actual source of the problem lies within the underlying java class files. The April CPU fails to properly load the newer patched classes, which means that these problems can still be exploited."
Litchfield also reported the resurfacing of a second issue first fixed last August. "On Windows, both 32bit and 64bit, a second problem exists whereby an attacker can run arbitrary SQL by abusing the CTXSYS.DRILOAD package to gain DBA privileges. This was discovered by multiple persons and was initially fixed in August 2004. However, the April Critical Patch Update copies the updated SQL script file to the wrong directory and if previous patches [either August 2004 or January 2005] have not applied then you will still be vulnerable to this attack even if the April CPU has been applied."
"DBAs should take remediation steps as soon as possible as exploit code was released into the public domain by Esteban Martinez Fayo of Appsec Inc.," Litchfield added.
An Oracle spokesperson said the first issue noted by Litchfield has been corrected. "Oracle issued an alert to customers
Other researchers say caution is warranted when installing any Oracle patch. "We always test Oracle patches against the bugs we have reported to them just to be sure the patches work," Cesar Cerrudo, CEO of Argeniss Information Security in Argentina, said in a posting to a security mailing list. "I personally recommend that you shouldn't install that patch on production systems before properly testing it for a couple of months or more since as we have seen Oracle doesn't have QA so you have to do it yourself."
The latest patches
Among the issues addressed yesterday are numerous security bugs in the Oracle Database, Oracle Application Server and Oracle E-Business Suite. Vulnerable products include:
- Oracle Database 10g Release 1, versions 10.1.0.2, 10.1.0.3, 10.1.0.4
- Oracle9i Database Server Release 2, versions 126.96.36.199, 188.8.131.52
- Oracle9i Database Server Release 1, versions 184.108.40.206, 220.127.116.11, 18.104.22.168 FIPS
- Oracle8i Database Server Release 3, version 22.214.171.124
- Oracle8 Database Release 8.0.6, version 126.96.36.199
- Oracle Enterprise Manager Grid Control 10g, versions 10.1.0.2, 10.1.0.3
- Oracle Enterprise Manager 10g Database Control, versions 10.1.0.2, 10.1.0.3, 10.1.0.4
- Oracle Enterprise Manager Application Server Control, versions 188.8.131.52, 184.108.40.206
- Oracle Application Server 10g (9.0.4), versions 220.127.116.11, 18.104.22.168
- Oracle9i Application Server Release 2, versions 22.214.171.124, 126.96.36.199
- Oracle9i Application Server Release 1, version 188.8.131.52
- Oracle Collaboration Suite Release 2, versions 184.108.40.206, 220.127.116.11
- Oracle E-Business Suite and Applications Release 11i, versions 11.5.1 through 11.5.10
- Oracle E-Business Suite and Applications Release 11.0
- Oracle Workflow, versions 11.5.1 through 18.104.22.168
- Oracle Forms and Reports, versions 22.214.171.124, 126.96.36.199
- Oracle JInitiator, versions 1.1.8, 1.3.1
- Oracle Developer Suite, versions 188.8.131.52, 9.0.4, 184.108.40.206, 9.0.5, 10.1.2
- Oracle Express Server, version 220.127.116.11
Oracle offered few details on the flaws, but a risk matrix is available on its site.
Chicago-based Integrigy Corp. said, "Customers with Internet-facing implementations of the Oracle E-Business Suite should consider applying these patches as soon as possible. It is possible that an attacker with only a Web browser and a network connection [either internally or externally] to Oracle E-Business Suite Web application servers can execute malicious SQL statements in the database as the APPS database account."