OAUG eLearning: January 2007 Critical Patch Update E-Business Suite Impact

For those of you who are OAUG members, I will be presenting an OAUG eLearning session on the Oracle Critical Patch Update January 2007 and the impact on the E-Business Suite.  This session will include a review of the security vulnerabilities fixed in the CPU, an analysis of the required CPU patches, and a discussion of a high-level patch strategy.  Depending the vulnerabilities fixed in the CPU, there may even be some demonstrations of the actual vulnerabilities.

Oracle Applications 11i User Password Weakness - Follow-up

Due to the number of client inquiries regarding my recent posting on the Oracle Applications 11i password decryption issue, we have written a whitepaper on the subject to provide more details and additional recommendations.  This issue is really a "perfect storm" with the convergence of (1) an inherent architectural weakness in the application, (2) generally accepted insec

October 2006 CPU and - Patches Finally Available

If you haven't noticed due to the holidays, Oracle has finally released the October 2006 Critical Patch Update (CPU) for on Unix/Linux and Windows.  These patches were released 75 days after the CPU and at least 45 days after the initial projected date.

The Database patch should be applied for all Oracle E-Business Suite databases running, even though the patch is not listed in the CPU documentation for the E-Business Suite.

11i: October 2006 Critical Patch Update Database Patch

Two weeks after the initial release of the October 2006 Critical Patch Update (CPU) Advisory, Oracle added information about the Oracle Database being vulnerable and about a patch being available in the future.  The patch release date keeps getting pushed back and is now scheduled for December 22 on Unix/Linux and December 15 for Windows (5 days ago).

Integrigy Oracle Listener Security Check Tool Updated

We have updated our free Oracle Database Listener Security Check tool that analyzes security of the Oracle Database TNS Listener to identify potential security issues.  The tool performs four basic checks for the Database Listener in a simple and user friendly way - (1) is a listener password set, (2) is ADMIN_RESTRICTIONS set, (3) is logging enabled, and (4) is LOCAL_OS_AUTHENTICATION enabled for Oracle 10g.  It is a single executable that can be run from any Windows XP/2000 PC, requires no Oracle client install, and can

Oracle Applications 11i User Password Weakness

The inherent weakness of the Oracle Applications 11i user password algorithm is a topic that every so often gets some attention.  It bubbles up and then is largely forgotten by most.  However, the issue doesn't go away and is very much alive today even in  See the references at the end of this post for a little history of the topic.  This password weakness (along with the APPLSYSPUB database account) is really a hold-over from client/server and is an inherent design flaw in the current architecture of Oracle Applications.

Evading Oracle IDS and Auditing Solutions

With the advent of legislative mandates like Sarbanes-Oxley (SOX) and the Health Insurance Portability and Accountability Act (HIPAA), the security and auditing of Oracle Databases has become much more of a priority for most organizations. A common solution has been to implement an Oracle-aware Intrusion Detection System (IDS) or auditing product to address these legislative mandates and increased auditor scrutiny.

October 2006 CPU and - Patches Available December 15

In a follow-up to my previous post regarding mystery patches for in the October 2006 Critical Patch Update, the CPU advisory was updated to include information about  However, the patches for are still not available and have an anticipated release date of December 15, 2006 (note: the initial release date was November 15, 2006).

Risk Associated with Cursor Snarfing

A new attack vector for the Oracle Database has been identified related to exploiting DBMS_SQL cursors that have not properly been closed.  The name for this type of attack is "Dangling Cursor Snarfing."  David Litchfield's paper on the topic can be found here.

Exploitation of this type of vulnerability is limited and requires ALL of the following conditions -

Week-long Disclosure of Unfixed Oracle Security Bugs Suspended

A security research firm based in Argentina, Argeniss, had announced a plan to publicly disclose an unfixed Oracle Database security bug every day for a week in December - "The Week of Oracle Database Bugs."  A disclosed unpatched security bug is referred to as a 0-day (or zero day).  Argeniss' motivation is "to demostrate Oracle isn't getting any better at securing its products."

Spoofing Oracle Session Information

Oracle Database session information includes database user name, operating system user name, host, terminal, IP address, module, program, timestamps, session ID, and other details. These values are critical to auditing and identifying the actual end-user. Many of the database session values can be “spoofed” by an attacker either to mask their true identity or to circumvent security and auditing measures.  It should come as no shock to anyone that many of these values can be spoofed since this fact has been widely discussed for years.


Subscribe to RSS

Add us to your favorite news reader.

Follow on Twitter

Get the latest updates.