# IT Security Briefing: Oracle Database Security Risks

- URL: https://www.integrigy.com/security-resources/it-security-briefing-oracle-database-security-risks
- Published: 2012-10-25
- Type: Webinar
- Products: Oracle Database
- Focus areas: Sensitive Data, Auditing
- Audience: IT Security
- CVE IDs: CVE-2010-2419
- PDF: https://www.integrigy.com/sites/default/files/Integrigy_IT_Security_Briefing_Security_Risks_Oracle_Database.pdf

> Webinar for IT security staff on the security risks in Oracle production databases, including protecting sensitive data, excessive user privileges and database activity monitoring, and the safeguards every database should have.

Most IT security staff are excellent at network and operating system security but have limited understanding of database security, so the security risks inherent in their company's Oracle production databases, such as protecting sensitive data, excessive user privileges and database activity monitoring, are not given serious consideration.

These slides, from November 2010, highlight three key risks, exploitation of Oracle security vulnerabilities, brute forcing of database passwords, and the lack and trustworthiness of database auditing, and the safeguards every production database should have. IT security teams can then judge the risk in their own databases and work with DBAs on a database security program.

## Key Points

- A PUBLIC bug can be exploited by anyone with a database account, such as Oracle E-Business Suite's generic APPLSYSPUB/PUB: in the October 2010 CPU, for 10.1.0.5 to 11.2.0.1 (all now desupported), CVE-2010-2419 in the Java Virtual Machine needed only CREATE SESSION, and its fix was `revoke execute on "oracle/aurora/vm/HotLoader" from public`.
- PCI-DSS 6.1 (PCI DSS is now at version 4.0) requires critical security patches within one month of release, as our whitepaper [Oracle E-Business Suite: Credit Cards and PCI Compliance](https://www.integrigy.com/security-resources/oracle-e-business-suite-credit-cards-and-pci-compliance) covers, yet most Oracle customers are 1 to 2 quarters behind, and an upgrade brings only its patch set's CPU, such as January 2010 for 11.2.0.1.
- The Oracle DES password hash, which 11g (now desupported) kept beside its new SHA-1 hash, is the same for a username and password in every database, so SYSTEM/MANAGER is always D4DF7931AB130E37, and brute forcing needs only the username and hash: an 8-character password takes 42 days on a desktop and 10 hours on a GPU.
- In a sample of 120 production databases, the default password remained for DBSNMP in 52%, OUTLN in 43% and CTXSYS in 32%, and databases are often cloned to test and development, so limit access to password hashes and change all database passwords in test and development.
- Enabling database auditing is the easy part, 5% of the effort against 80% for monitoring, alerting, reporting and reviewing, and some session data in native audit trails (traditional auditing, which Oracle desupported in 23ai (now 26ai) in favor of Unified Auditing) can be spoofed, so understand audit data before relying on it.
- Checklists such as the CIS Oracle Benchmark and DISA Oracle STIG are an excellent baseline but often conflict with the application, so build a database security program: a strategy, a documented configuration and security standard, products for specific problems, and "virtual perimeters" limiting and segregating access at the network, OS, database and application layers.
