Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Perimeter

8/9/2010
07:30 PM
Adrian Lane
Adrian Lane
Commentary
50%
50%

How To Protect Oracle Database Vault

In Esteban Martinez Fayo's "Hacking and Protecting Oracle Database Vault" session at Black Hat USA in Las Vegas a couple weeks ago, he used several exploit methods that could be used to disable Oracle Data Vault. Each exploit provided an avenue by which he could hack the database. With each exploit he performed the same hack: rename the dynamically linked library that implemented all Oracle Database Vaults functions.

In Esteban Martinez Fayo's "Hacking and Protecting Oracle Database Vault" session at Black Hat USA in Las Vegas a couple weeks ago, he used several exploit methods that could be used to disable Oracle Data Vault. Each exploit provided an avenue by which he could hack the database. With each exploit he performed the same hack: rename the dynamically linked library that implemented all Oracle Database Vaults functions.These are known exploits, and in the case of the buffer overflow attack, a patched problem. The demonstration was not some tricky new exploit, but common attack vectors. The real point of the presentation is not about a particular exploit, but the fact that Database Vault functions could be removed entirely should any of these exploits -- or valid permissions -- be available. Once the DLL is renamed, the next database restart will occur normally, but the database will resume operation without Database Vault functions.

Some of the people I spoke with after the show did not understand how this could be the case, but unless you are looking at the log files to detect this type of system event, it will go entirely unnoticed. User access, DBA roles, and multifactor authentication requirements simply vanish.

My interest in pointing this out is not the novelty of the attack, but rather to point out that you probably have tools in your house to detect or even prevent this type of exploit. The presentation lacked some of the detection and prevention tactics, so I will mention a few here:

1. Every commercial database vulnerability assessment scanner on the market checks for the exploits mentioned above. New variations may be found, but most of the avenues for exploitation can be checked and verified fixed.

2. This is why constantly checking for patches and keeping current is so important -- two of the three attacks could be thwarted with current patches.

3. Injection attacks launch code with the same privileges that the database runs under, so it's not like access controls are going to help with that. 4. Stored procedures, external or internal, are a handy tool for administrators. And they are really dangerous. They remain a principle avenue for exploit, so external stored procedures should be disabled and changes to internal procedures carefully monitored.

5. File-permissions monitoring, either through assessment, database assessment, or file monitoring tools, will detect the attack.

6. Permissions monitoring is a pain in the -- well, you know. But checking stored procedure settings and user access maps to stored procedures is necessary. There are commercial tools to automate, or you can write some simple scripts to detect, but make sure this is in your arsenal.

If you are not sure your policies cover this threat, then go check.

Adrian Lane is an analyst/CTO with Securosis LLC, an independent security consulting practice. Special to Dark Reading. Adrian Lane is a Security Strategist and brings over 25 years of industry experience to the Securosis team, much of it at the executive level. Adrian specializes in database security, data security, and secure software development. With experience at Ingres, Oracle, and ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Why Cyber-Risk Is a C-Suite Issue
Marc Wilczek, Digital Strategist & CIO Advisor,  11/12/2019
The Cold Truth about Cyber Insurance
Chris Kennedy, CISO & VP Customer Success, AttackIQ,  11/7/2019
Black Hat Q&A: Hacking a '90s Sports Car
Black Hat Staff, ,  11/7/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
7 Threats & Disruptive Forces Changing the Face of Cybersecurity
This Dark Reading Tech Digest gives an in-depth look at the biggest emerging threats and disruptive forces that are changing the face of cybersecurity today.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-5230
PUBLISHED: 2019-11-13
P20 Pro, P20, Mate RS smartphones with versions earlier than Charlotte-AL00A 9.1.0.321(C00E320R1P1T8), versions earlier than Emily-AL00A 9.1.0.321(C00E320R1P1T8), versions earlier than NEO-AL00D NEO-AL00 9.1.0.321(C786E320R1P1T8) have an improper validation vulnerability. The system does not perform...
CVE-2019-5231
PUBLISHED: 2019-11-13
P30 smartphones with versions earlier than ELLE-AL00B 9.1.0.186(C00E180R2P1) have an improper authorization vulnerability. The software incorrectly performs an authorization check when a user attempts to perform certain action. Successful exploit could allow the attacker to update a crafted package.
CVE-2019-5233
PUBLISHED: 2019-11-13
Huawei smartphones with versions earlier than Taurus-AL00B 10.0.0.41(SP2C00E41R3P2) have an improper authentication vulnerability. Successful exploitation may cause the attacker to access specific components.
CVE-2019-5246
PUBLISHED: 2019-11-13
Smartphones with software of ELLE-AL00B 9.1.0.109(C00E106R1P21), 9.1.0.113(C00E110R1P21), 9.1.0.125(C00E120R1P21), 9.1.0.135(C00E130R1P21), 9.1.0.153(C00E150R1P21), 9.1.0.155(C00E150R1P21), 9.1.0.162(C00E160R2P1) have an insufficient verification vulnerability. The system does not verify certain par...
CVE-2010-4177
PUBLISHED: 2019-11-12
mysql-gui-tools (mysql-query-browser and mysql-admin) before 5.0r14+openSUSE-2.3 exposes the password of a user connected to the MySQL server in clear text form via the list of running processes.