# When You Can’t Apply Oracle Security Patches

- URL: https://www.integrigy.com/security-resources/when-you-cant-apply-oracle-security-patches
- Published: 2013-06-26
- Type: Webinar
- Products: Oracle E-Business Suite, Oracle Database
- Focus areas: Oracle Critical Patch Updates
- Audience: DBA, IT Security
- Applies to: EBS 11i, EBS 12.0, EBS 12.1, DB 10g, DB 11g
- PDF: https://www.integrigy.com/sites/default/files/Integrigy%20When%20You%20Can%25E2%2580%2599t%20Apply%20Oracle%20Security%20Patches%20v1.pdf
- Recording: https://www.youtube.com/watch?v=rrmZxWWD7WQ

> Webinar on why Oracle Database and E-Business Suite security patches go unapplied, how installs and upgrades can reset the patch level, and the mitigating controls for organizations quarters or years behind.

Oracle Database Critical Patch Updates (CPUs) are not applied to many production databases, leaving organizations quarters or years behind on security patches. Applying and testing them takes significant effort, a patch may require a database upgrade the application doesn't support, there may be no downtime window, and IT management and DBAs may not make them a priority.

We discuss these common challenges, strategies to overcome them, and the mitigating controls that protect the Oracle Database and Oracle E-Business Suite when patches go unapplied, matched to the type of user who could exploit each vulnerability. DBAs and IT security teams can then judge their exposure and choose controls.

## Key Points

- A database or EBS release includes only the CPU current at its release, such as July 2010 for EBS 12.1.3, so always apply the latest CPU with every installation or upgrade: one client's February 2013 upgrade to 11.2.0.2 reset its database to January 2011, and by April 2013 it was 9 CPUs and 29 vulnerabilities behind.
- Patch sets get CPUs only until a terminal CPU (October 2013 for 11.2.0.2; Oracle Database 11.2 is now desupported); in production, use the latest SPU, only security fixes and low risk, or the PSU from the last tested database, which adds priority fixes and, once applied, must be followed only by PSUs until the next upgrade.
- Database risk depends on whether an attacker has or can obtain an account: of the 29 unpatched 11.2.0.2 bugs, 9 need no account (1 in O5LOGON authentication, 7 denial of service), 7 only PUBLIC privileges, 6 usually CREATE PROCEDURE, and 7 high privileges such as SYSDBA or local OS access.
- Without CPUs, block direct database access with an enterprise firewall or VPN, or by IP address with SQL*Net Valid Node Checking or Oracle Connection Manager; use only named accounts and no generic read-only accounts, limit privileges in production, and add Oracle Database Vault, an external database auditing solution and OS access for production limited to DBAs.
- In the 12.1.3 CPU risk mapping (EBS 12.1 is now desupported), 18 bugs were open to external unauthenticated users of modules such as iSupplier and iStore, even with the URL firewall, 16 of them high risk, and 34 to internal unauthenticated users; upgrading from 11i to 12.x reverses all CPU fixes, and from 12.0 to 12.1 most.
- Without CPUs, enable the EBS URL firewall and external responsibilities, following the DMZ configuration in MOS 380490.1 (R12) or 287176.1 (11i, now desupported), limit access to privileged responsibilities, and add our [AppDefend](https://www.integrigy.com/products/appdefend) application firewall, which detects SQL injection, XSS and known EBS vulnerabilities and limits EBS modules more flexibly than the URL firewall.
